Github vs MCP Server Azure Devops

A side-by-side look at the Github and MCP Server Azure Devops MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Github logoGithubVersion Control · Local subprocess (stdio)GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)63GoodAuth: not declaredMCP Server Azure Devops logoMCP Server Azure DevopsVersion Control · Local subprocess (stdio)Azure DevOps integration for repository management, work items, and pipelines.67GreatAuth: other

Verdict: choose Github for version control work as a local process; choose MCP Server Azure Devops for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Github logoChoose Github when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search_repos, get_repo, list_repo_issues.
Explore Github

MCP Server Azure Devops logoChoose MCP Server Azure Devops when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You have the keys it needs: AZURE_DEVOPS_ORG_URL, AZURE_DEVOPS_AUTH_METHOD, AZURE_DEVOPS_PAT, AZURE_DEVOPS_DEFAULT_PROJECT, AZURE_DEVOPS_API_VERSION, AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET.
  • You want tools like get_me, list_organizations, list_projects.
Explore MCP Server Azure Devops

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGithub logoGithubMCP Server Azure Devops logoMCP Server Azure Devops
CategoryVersion ControlVersion Control
Quality signal63/100 · Good67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredother
PricingNot declaredFree
Required env varsNone listedAZURE_DEVOPS_ORG_URLAZURE_DEVOPS_AUTH_METHODAZURE_DEVOPS_PATAZURE_DEVOPS_DEFAULT_PROJECTAZURE_DEVOPS_API_VERSIONAZURE_TENANT_IDAZURE_CLIENT_IDAZURE_CLIENT_SECRET
Verified ownerCommunity listingCommunity listing
GitHub stars0399
Directory activity 8 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools933

Tools & capabilities

Github tools 9

  • search_reposSearch GitHub repositories by keyword. Returns repo name, description, star count, forks, primary language, and URL. Use when exploring projects or finding code implementations.
  • get_repoLook up ONE named repository by its owner/repo slug — "facebook/react", "torvalds/linux", "vercel/next.js". Use this whenever the repository is named in the question. Answers how many stars / forks / watchers a repo has, what license and language it uses, its topics, description, open issue count, its default branch, and when it was last pushed (pushed_at).
  • list_repo_issuesList issues for a GitHub repository by owner and repo name; filters pull requests out automatically. Returns issue number, title, state, labels, author, comment count, URL, and timestamps. Defaults to open issues.
  • get_userGet a GitHub user's public profile info. Returns name, bio, company, location, public repo count, followers, and social links. Specify username (e.g., username="torvalds").
  • get_file_contentsRead a file from a PUBLIC GitHub repository (or list a directory) by path. PREFER OVER WEB SEARCH for "show me the README / package.json / <file> of <repo>", "read <path> from <owner/repo>", inspecting source or config files. Pass owner + repo + path (omit path or "" for the repo root listing). Optional ref = branch/tag/commit SHA. Returns decoded text for files (capped ~60k), or a directory listing of {name, path, type, size}.
  • search_codeSearch CODE across public GitHub repositories — find where a function/symbol/string is defined or used. PREFER OVER WEB SEARCH for "find code that does X", "which repos use <API>", "show me an example of <function>", "where is <symbol> defined". Supports GitHub code-search qualifiers right in the query: repo:owner/name, org:name, user:name, language:go, filename:Dockerfile, path:src, extension:ts, in:file. Returns matching files with repo, path, and URL. Note: indexes the default branch only, ignores very common terms, and is capped at ~10 searches/minute.
  • get_releasesGet the latest release and recent release history for a repository — the canonical way to answer "what is the latest version of <project>", "when was <repo> last released", "what changed in the newest release". Returns the latest published stable release (tag, name, date, prerelease flag, release notes, downloadable assets with download counts) plus recent releases. Falls back to git tags for repos that tag but do not cut formal releases.
  • list_commitsList recent commits on a repository to see latest activity, what changed, and who is committing. PREFER OVER WEB SEARCH for "what are the recent commits to <repo>", "when was <owner/repo> last updated", "latest changes in <repo>". Optional sha (branch/tag/commit to start history from), path (only commits touching that file/dir), and since/until ISO timestamps. Returns sha, message, author, and date per commit.
  • github_trending_reposTrending GitHub repositories — what is hot, popular, and taking off on GitHub right now. Answers "what are the top trending GitHub repos this week", "what is hot on GitHub today", "popular new repositories this month", "trending Rust / Python / AI projects", "which GitHub projects blew up recently". Two modes: mode="new" (default) ranks repositories CREATED inside the time window by star count — the projects that blew up this week — and mode="active" ranks repositories PUSHED inside the window by star count, surfacing established projects under heavy development. Set the window with since (day, week, or month), filter with language, add free-text query keywords such as "llm" or "agent", and raise a min_stars floor. Returns full_name, description, language, stars, forks, created and pushed dates, topics, and URL per repo. Computed live from the GitHub Search API; github.com/trending ranks by stars GAINED during the period using an unpublished algorithm that the public API keeps private, so ordering differs and every response says so in its caveat field.

MCP Server Azure Devops tools 33

  • get_meGet details of the authenticated user (id, displayName, email) (Azure DevOps Services only)
  • list_organizationsList all accessible organizations (Azure DevOps Services only)
  • list_projectsList all projects in an organization
  • get_projectGet details of a specific project
  • get_project_detailsGet comprehensive details of a project including process, work item types, and teams
  • list_repositoriesList all repositories in a project
  • get_repositoryGet details of a specific repository
  • get_repository_detailsGet detailed information about a repository including statistics and refs
  • get_file_contentGet content of a file or directory from a repository
  • get_repository_treeList a repository's file tree from any path and depth
  • create_branchCreate a new branch from an existing one
  • create_commitCommit multiple file changes to a branch using unified diffs or search/replace instructions
  • +21 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Github

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "github-3": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-github"
      ]
    }
  }
}

MCP Server Azure Devops

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tiberriver256-mcp-server-azure-devops": {
      "command": "npx",
      "args": [
        "-y",
        "@tiberriver256/mcp-server-azure-devops"
      ],
      "env": {
        "AZURE_DEVOPS_ORG_URL": "YOUR_AZURE_DEVOPS_ORG_URL_HERE",
        "AZURE_DEVOPS_AUTH_METHOD": "YOUR_AZURE_DEVOPS_AUTH_METHOD_HERE",
        "AZURE_DEVOPS_PAT": "YOUR_AZURE_DEVOPS_PAT_HERE",
        "AZURE_DEVOPS_DEFAULT_PROJECT": "YOUR_AZURE_DEVOPS_DEFAULT_PROJECT_HERE",
        "AZURE_DEVOPS_API_VERSION": "YOUR_AZURE_DEVOPS_API_VERSION_HERE",
        "AZURE_TENANT_ID": "YOUR_AZURE_TENANT_ID_HERE",
        "AZURE_CLIENT_ID": "YOUR_AZURE_CLIENT_ID_HERE",
        "AZURE_CLIENT_SECRET": "YOUR_AZURE_CLIENT_SECRET_HERE"
      }
    }
  }
}

Frequently asked questions

Github is categorized under Version Control and uses a local stdio subprocess. MCP Server Azure Devops belongs to Version Control and uses a local stdio subprocess. Pick Github for version control work and MCP Server Azure Devops for version control.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Github has no declared pricing — check the project's own site. MCP Server Azure Devops is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add github-3 and tiberriver256-mcp-server-azure-devops as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Github has a quality signal of 63/100 (Good) with 8 views, 0 installs and 0 GitHub stars. MCP Server Azure Devops has 67/100 (Great) with 7 views, 0 installs and 399 GitHub stars.