Head to head · Code repo · October 2026 research run

Azure DevOps MCP Server vs GitHub MCP Server

GitHub MCP Server scores 70.3 (BB) on agent readiness against Azure DevOps MCP Server's 66.3 (B), and leads in 5 of 7 scored categories. Azure DevOps MCP Server leads on reliability. Both do code repo.

Which one, for what

Azure DevOps MCP Server B

Good 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 60

Watch for

The remote server was announced as a public preview on 17 March 2026 and no general availability notice was found

GitHub MCP Server BB

Good 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

Watch for

92 tools and about 30,000 tokens with everything enabled; the default set alone is 45 tools

Score by category

CategoryWeight this runAzure DevOps MCP ServerGitHub MCP ServerEdge
Reliability16%207260Azure DevOps MCP Server +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26483GitHub MCP Server +19
Agent ergonomics13%16.27078GitHub MCP Server +8
Security & auth14%17.58184GitHub MCP Server +3
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88093GitHub MCP Server +13
Transparency & trust7%8.87983GitHub MCP Server +4
Negative events≤15-3-3
Total66.3 · B70.3 · BB

Facts side by side

FactAzure DevOps MCP ServerGitHub MCP Server
KindMCP serverMCP server
VendorMicrosoftGitHub
Hosted endpointhttps://mcp.dev.azure.com/{organization}https://api.githubcopilot.com/mcp/
TransportsStreamable HTTP, stdiostdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFree
x402nono
LicenceMIT for the local server in the repository. The hosted remote server is a Microsoft online service under the customer's Azure DevOps termsMIT
Tools exposed4892
Read-only variant documentedyesyes
llms.txtnoyes
MCP registrynot listedio.github.github/github-mcp-server
Last release2026-09-092026-10-01
Terms last updatedno date given2026-04-27
Privacy policy last updated2026-09-012026-04-27
Customer content may train modelsyesyes, with an opt-out
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2k stars, 120k npm/wk32k stars
Agent reviewsnone4/5 (2)

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. The remote server is still labelled public preview, and Claude Code and Cursor need a custom Entra app registration with admin consent before they can use it.

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

  1. 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
  2. Send X-MCP-Readonly: true for read tasks and X-MCP-Toolsets: repos,wit to cut the tool list. Don't combine X-MCP-Toolsets with X-MCP-Tools
  3. Name the project in each call. A missing project is the error the vendor reports most often
  4. For headless runs use the local package with --authentication envvar and a token in ADO_MCP_AUTH_TOKEN. The default interactive sign-in fails without a browser
  5. 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

  1. Connect to https://api.githubcopilot.com/mcp/x/<toolset>/readonly for read tasks; write tools are absent rather than discouraged
  2. Send X-MCP-Toolsets: repos,issues,pull_requests to trim the tool list instead of loading 45 or more tools
  3. Pass fields on list and search calls to cut response size, and page with perPage up to 100
  4. On 403 or 429 read retry-after or x-ratelimit-reset, and wait at least a minute if neither is set
  5. 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 70.3 (BB) on agent readiness against Azure DevOps MCP Server's 66.3 (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

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.