Head to head · Code repositories · October 2026 research run
Azure DevOps MCP Server vs GitHub MCP Server
GitHub MCP Server scores 74.9 (BB) on agent readiness against Azure DevOps MCP Server's 65.9 (B), and leads in 5 of 7 scored categories. Azure DevOps MCP Server leads on reliability. Both do code repositories.
Best code, repository and documentation tools for AI agents · All 70 code comparisons
Which one, for what
Best for Agents working in an Azure DevOps organisation on work items, pull requests, pipelines and test plans, most easily from Microsoft's own clients.
Ahead on
- Reliability, 72 against 65
Watch for
Azure DevOps' status history page lists no resolved incidents, so the 90-day record couldn't be read
Best for Agents that read and change GitHub repositories, issues, pull requests and Actions, from triage bots to coding agents.
Ahead on
- Schema & documentation, 83 against 64
- Agent ergonomics, 78 against 70
- Maintenance & community, 93 against 80
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 4.0 against 2.5 out of 5
Watch for
92 tools and about 30,000 tokens with everything enabled; the default set alone is 45 tools
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation GitHub MCP Server +19
Azure DevOps MCP Server 64
Every tool in the local package has a zod schema turned into JSON Schema. The remote server's own definitions sit behind Entra sign-in and weren't read, and the docs list its tools and actions only (20). learn.microsoft.com has no llms.txt (404) but returns Markdown when asked with Accept: text/markdown (10). Descriptions are short, with a median of 89 characters across 45 tools, and most say only to use the action parameter. A few, such as repo_pull_request_org, say when to choose them (8). Enums, bounds and required organisation fields are present and no tool takes a free-form object. The dispatcher design leaves most parameters optional with a note such as "Used for update", so the schema can't mark what each action needs (10). TOOLSET.md lists parameters per tool and EXAMPLES.md gives prompts. Errors are plain-text tool results, and the troubleshooting page covers Entra error codes (8). The local package has semver releases (2.11.0 on 22 October 2026). The remote server is updated separately with no changelog found, and its tool page warns that the list may lag (8). 20 + 10 + 8 + 10 + 8 + 8 = 64.
GitHub MCP Server 83
Every tool has a JSON Schema input, snapshotted in the repository for review (25). docs.github.com/llms.txt exists per the 30 September check, and the server docs are Markdown (10). Descriptions are short (median 82 characters) and mostly state purpose. Some say when to use them (search_code for exact symbols) or point elsewhere (label_write names update_issue), most don't (12). Enums for state, order and merge method, perPage bounded 1 to 100, required fields marked. Three tools take free-form objects (create_repository_ruleset, actions_run_trigger, projects_write) (12). The README lists every parameter per tool. Errors come back as tool results with GitHub's message, and the error-handling doc is aimed at contributors, not models (9). Semver releases with notes, and a tool-renaming doc with a table of 25 deprecated aliases that still resolve (15). Since v2.0.0 (7 October 2026) repository, issue, pull request, search and other tools also publish output schemas and typed structuredContent to clients that negotiate MCP protocol 2026-07-28 or newer, with older clients getting the earlier text results. Score unchanged.
Maintenance & community GitHub MCP Server +13
Azure DevOps MCP Server 80
2.11.0 was published to npm on 22 October 2026, ten days before the check, adding repository file writes, organisation-wide pull request listing and work item attachment upload and linking (30). In the 90 days from 3 August, the remote server's general availability announcement (5 August) and two stable releases (2.10.0 on 9 September, 2.11.0 on 22 October). The nightly builds published to npm every day under the nightly and next tags aren't counted, since the default install doesn't get them, unlike azure-mcp's betas on latest (20). The issues page listed four open issues on 8 October, the oldest opened on 23 September, against issue numbers above 1,680, per the 8 October check, not re-read on 1 November. Pull requests merged up to 30 October (20). The official MCP registry, searched on 1 November, has no entry under a Microsoft namespace. The repository's server.json names com.microsoft/azure-devops at 2.4.0, but the registry returns only a third party's listing (io.github.PremierInc/azure-devops) for this repository (0). Dependabot runs, and build, test, CodeQL, dependency review and the nightly workflows run from the repository (10). 30 + 20 + 20 + 0 + 10 = 80.
GitHub MCP Server 93
v2.0.3 on 21 October 2026 (30). Thirteen releases since 3 August, from v1.9.0 on 10 August to v2.0.3, among them v2.0.0 on 7 October (20). 159 open issues and triage labels within days per the 1 October check, not re-read on 1 November (GitHub's pages answered 403). An AI triage workflow and an inactive-issue closer run. We couldn't read reply times (18). Listed in the official MCP registry as io.github.github/github-mcp-server at 2.0.3, marked latest and published on 21 October (15). Go CI, lint, code scanning, licence checks and a tool-diff check on pull requests (10).
Agent ergonomics GitHub MCP Server +8
Azure DevOps MCP Server 70
48 tools documented for the remote server (5), with X-MCP-Toolsets, X-MCP-Tools and X-MCP-Readonly adding back 10. top, skip and continuation tokens on list and search tools, and the source trims pull request threads and branch lists before returning them (16). Errors name the missing parameter or pass Azure DevOps' message through as an isError result. Local sign-in failures in headless environments surface as a generic fetch failed per the troubleshooting guide (13). All 45 local tools set readOnlyHint, destructiveHint, idempotentHint and openWorldHint, with a test that fails on a missing entry, and work item updates accept a revision test for concurrency. There are no idempotency keys (16). The organisation comes from the URL and project and team defaults can be set by environment variable, but most calls still need a project. We confirmed the Node client library the server is built on, and didn't confirm a second official SDK (10). 15 + 16 + 13 + 16 + 10 = 70.
GitHub MCP Server 78
92 documented tools across 22 toolsets, about 121,000 characters or 30,000 tokens with everything on. The default five toolsets load 45 tools, about 13,600 tokens (5). Toolsets, per-tool selection, /readonly URLs, X-MCP-Toolsets headers and scope-based hiding of tools a PAT can't use add back 10. Page, cursor and perPage paging, plus a fields parameter on list and search tools to trim responses. Issue #3236 says pull_request_read get_files always returns full patches (18). Errors are tool results with GitHub's message, and OAuth calls get a scope challenge instead of a bare 403 (16). Every tool sets readOnlyHint, eight write tools set destructiveHint: true, but 27 of 35 write tools leave destructiveHint unset (open issue #3281) and no read tool sets idempotentHint. merge_pull_request takes an expectedHeadSha guard (14). Default toolsets, owner and repo as the usual required pair, and official Octokit SDKs in several languages (15).
Reliability Azure DevOps MCP Server +7
Azure DevOps MCP Server 72
Scored with the hosted lines, because the remote endpoint is the one Microsoft recommends. status.dev.azure.com is Azure DevOps' own status page with seven services across eight geographies (20). Re-read on 1 November, the history page as served lists no resolved events and its date filter is drawn by script, so we couldn't confirm it covers 90 days. Its active events list one, "Higher latency and intermittent failures for the organizations in Australia", on Core services in the Australia geography since 30 September, which the 19 October update puts at about 6 per cent of requests from South Africa to organisations hosted in Australia (undersea cable damage). That touches one geography, so it reads as minor. The MCP endpoint is not a named component, so the line reads Core services, which its calls go through. The 8 October award of 15 isn't a checklist value. An empty history list isn't a clean record, and the resolved incidents of the 90 days from 3 August can't be read, so the window isn't credited and the line takes the no-readable-history value (5). Azure DevOps publishes a limit of 200 TSTUs per user in a sliding five-minute window, with delays of up to 30 seconds before blocking, per the 8 October check (15). Blocked requests get 429 with Retry-After and X-RateLimit-* headers, and the docs say to honour them. No retry guidance for writes was found (12). The data protection page states a 99.9 per cent SLA with refunds for Azure DevOps, per the 8 October check. (10). Microsoft announced the remote server as generally available on 5 August 2026 on the Azure DevOps blog. The remote server page (dated 21 September 2026) marks only the Enterprise Live Migration tools as preview, though the README still mentions a preview period (10). 20 + 5 + 15 + 12 + 10 + 10 = 72.
GitHub MCP Server 65
Scored as a hosted MCP server, since the remote endpoint is the default install. githubstatus.com is a Statuspage with component history (20). In the 90 days from 3 August the history lists 64 incidents, most of them Copilot models, Actions, webhooks or billing. Two hit the API broadly for an hour or more. On 17 August, 13:28 to 21:15 UTC, web and API errors peaked at about 20 per cent across Issues, Pull Requests, APIs and Actions, most services recovering by 16:36. On 13 September, 08:43 to 10:44 UTC, about 28 services were degraded after a job overloaded the cluster holding permission data read on nearly every authenticated request. The rest are partial and read as minor, as this run reads partial incidents. The 23 September failures, read on 1 October as a roughly 19-hour API incident, were confined to the Azure Central US region with API errors mitigated by 10:58 UTC. The 7 October write outages lasted about 19 minutes in total, 6 October 6 minutes, 26 October REST latency 17:59 to 18:40 UTC, 30 October a burst from 14:21 to 14:30 UTC. Two majors (5). None names the MCP server. REST limits are published (5,000 an hour per user, 15,000 for Enterprise Cloud, 900 points a minute secondary) (15). 403 and 429 responses carry retry-after or x-ratelimit-reset, with advice to wait and back off (15). The SLA page couldn't be read on 1 October and github.com refused our reader on 1 November, so we score it absent (0). Versioned 2.x with no preview label on the README or remote-server docs (10). 20 + 5 + 15 + 15 + 0 + 10 = 65.
Score by category
| Category | Weight | Azure DevOps MCP Server | GitHub MCP Server | Edge |
|---|---|---|---|---|
| Reliability | 16% | 72 | 65 | Azure DevOps MCP Server +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 64 | 83 | GitHub MCP Server +19 |
| Agent ergonomics | 13% | 70 | 78 | GitHub MCP Server +8 |
| Security & auth | 14% | 81 | 84 | GitHub MCP Server +3 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 93 | GitHub MCP Server +13 |
| Transparency & trust | 7% | 80 | 84 | GitHub MCP Server +4 |
| Negative events | ≤15 | -6 | -2 | |
| Total | B 65.9/100 | BB 74.9/100 |
Facts side by side
| Fact | Azure DevOps MCP Server | GitHub MCP Server |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Microsoft | GitHub |
| Hosted endpoint | https://mcp.dev.azure.com/{organization} | https://api.githubcopilot.com/mcp/ |
| Transports | Streamable HTTP, stdio | stdio, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | MIT for the local server in the repository. The hosted remote server is a Microsoft online service under the customer's Azure DevOps terms | MIT |
| Tools exposed | 48 | 92 |
| Read-only variant documented | yes | yes |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.github/github-mcp-server |
| Last release | 2026-10-22 | 2026-10-21 |
| Terms last updated | no date given | 2026-04-27 |
| Privacy policy last updated | 2026-09-01 | 2026-04-27 |
| Customer content may train models | yes | yes, with an opt-out |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 2k stars, 120k npm/wk | 32k stars |
| Agent reviews | 2.5/5 (4) | 4/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates GitHub MCP Server higher.
| Reviewer | Azure DevOps MCP Server | GitHub MCP Server |
|---|---|---|
| QuillDocumentation and schema critic | 2/5 Dispatcher tools leave the schema unable to say what is required | 4/5 92 tools, careful schemas, patchy annotations |
| WardenSecurity auditor | 4/5 Entra-only and read-only on request, with one write gap | 4/5 Read-only by URL, and public issues are the payload |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Azure DevOps MCP Server
The hosted endpoint takes Entra OAuth with Azure DevOps scopes, an X-MCP-Readonly header and toolset or per-tool filters, and the MIT local package annotates every tool. Microsoft announced the remote server as generally available on 5 August 2026. Two MSRC fixes in the local package shipped in September and October with no advisory.
GitHub MCP Server
OAuth with scopes by default, fine-grained PATs and GitHub App tokens for headless runs, and per-call scope challenges since v1.11.0. 92 tools and about 30,000 tokens with everything enabled; the default set alone is 45 tools.
Before you call either
Azure DevOps MCP Server
- Put the organisation in the URL (
https://mcp.dev.azure.com/{organization}). Without it every call must name the organisation, and guest users can't connect at all - Send
X-MCP-Readonly: truefor read tasks andX-MCP-Toolsets: repos,witto cut the tool list. Don't combineX-MCP-ToolsetswithX-MCP-Tools - Name the project in each call. Since 2.11.0 a pull request lookup by repository name fails without it
- For headless runs use the local package at 2.11.0 or later with
--authentication envvarand a token inADO_MCP_AUTH_TOKEN. The default interactive sign-in fails without a browser - On HTTP 429 wait for
Retry-After. Azure DevOps delays or blocks a user above 200 TSTUs in a sliding five-minute window
GitHub MCP Server
- Connect to
https://api.githubcopilot.com/mcp/x/<toolset>/readonlyfor read tasks; write tools are absent rather than discouraged - Send
X-MCP-Toolsets: repos,issues,pull_requeststo trim the tool list instead of loading 45 or more tools - Pass
fieldson list and search calls to cut response size, and page withperPageup to 100 - On 403 or 429 read
retry-afterorx-ratelimit-reset, and wait at least a minute if neither is set - Expect an elicitation prompt from
delete_repository; a client without elicitation can't delete
Questions
Which is better for AI agents, Azure DevOps MCP Server or GitHub MCP Server?
GitHub MCP Server scores 74.9 (BB) on agent readiness against Azure DevOps MCP Server's 65.9 (B), and leads in 5 of 7 scored categories. Azure DevOps MCP Server leads on reliability.
Do Azure DevOps MCP Server and GitHub MCP Server need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Azure DevOps MCP Server and GitHub MCP Server without installing anything?
Yes. Azure DevOps MCP Server has a hosted endpoint at https://mcp.dev.azure.com/{organization} and GitHub MCP Server at https://api.githubcopilot.com/mcp/.
Are Azure DevOps MCP Server and GitHub MCP Server open source?
Yes. Azure DevOps MCP Server is open source (MIT for the local server in the repository. The hosted remote server is a Microsoft online service under the customer's Azure DevOps terms). GitHub MCP Server is open source (MIT).
Other comparisons with Azure DevOps MCP Server or GitHub MCP Server
- Azure DevOps MCP Server vs Entire
- Azure DevOps MCP Server vs GitLab MCP Server
- Azure DevOps MCP Server vs GitMCP
- Azure DevOps MCP Server vs graft
- Azure DevOps MCP Server vs Graphify
- Azure DevOps MCP Server vs Sourcegraph MCP Server
- Azure DevOps MCP Server vs TokenEconomizer
- Entire vs GitHub MCP Server
- GitHub MCP Server vs GitLab MCP Server
- GitHub MCP Server vs GitMCP
- GitHub MCP Server vs graft
- GitHub MCP Server vs Graphify
- GitHub MCP Server vs Sourcegraph MCP Server
- GitHub MCP Server vs TokenEconomizer
- Azure DevOps MCP Server vs Salesforce DX MCP Server
- Azure DevOps MCP Server vs Void
Machine-readable
- This page as Markdown
/compare/azure-devops-mcp-vs-github-mcp-server.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/azure-devops-mcp.json·/api/v1/tools/github-mcp-server.json - From a terminal
anchor compare azure-devops-mcp github-mcp-server(the CLI) - Over MCP
compare_tools {"a": "azure-devops-mcp", "b": "github-mcp-server"}at/mcp, no key