Ranked roundup · Azure DevOps
Best MCP Server for Azure DevOps
Picking an MCP server for Azure DevOps is one of the easier calls in this category, because Microsoft ships an official one. The microsoft/azure-devops-mcp repo sits at 1,990 stars, MIT-licensed, with commits landing the day before we checked, and it covers nine toolsets — work items, repos, pipelines, wiki, test plans, search, Advanced Security — plus a Microsoft-hosted remote endpoint at mcp.dev.azure.com. The catch: the remote endpoint's Entra ID auth doesn't work with Claude Code, Claude Desktop, or Codex, and the whole thing targets cloud-hosted Azure DevOps Services only. That leaves real gaps for the community to fill — Tiberriver256's server for on-prem Azure DevOps Server, Vortiago's for Python shops — and Zapier for people who want a hosted, no-code path. We ranked all four on verifiable criteria: official status, commit recency, adoption, auth model, and documented coverage. Nobody paid for placement, and we don't invent benchmark scores.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Official · Microsoft
Anyone on cloud-hosted Azure DevOps Services — the default choice.
Nine toolsets: core (projects/teams), work (iterations/capacity), work items (WIQL, batch updates, linking), repos (PRs, branches, file content, commit search), pipelines (builds, logs, artifacts, run/create), wiki (read/write, search), test plans, Advanced Security alerts, plus code/wiki/work-item full-text search. Supports read-only mode and per-toolset filtering via headers.
Remote: Microsoft-hosted at mcp.dev.azure.com (streamable HTTP), no install. Local: stdio via npx @azure-devops/mcp, Node.js 20+. · Remote: Microsoft Entra ID (OAuth), requires an Entra-tenant-backed organization. Local: Azure DevOps PAT or Entra ID sign-in. · MIT · 1,990★
- Claude Code, Claude Desktop, and Codex cannot authenticate to the remote server (Entra ID lacks the dynamic client registration flow they need) — those clients must run the local stdio server instead
- Remote endpoint requires an Entra-tenant-backed organization; standalone Microsoft-account (MSA) orgs are not supported
- Cursor needs a custom Entra app registration with admin consent to use the remote endpoint
- Cloud only — official docs target Azure DevOps Services, not on-prem Azure DevOps Server
- The repo still refers to the remote server's preview period, and the Enterprise Live Migration toolset is explicitly in preview
- A recent tool consolidation renamed existing tools — a breaking change for agents; Microsoft suggests pinning @azure-devops/[email protected] if it bites
- The local server is on a maintenance path: Microsoft says new development focuses on the remote server and local users should plan migration
- Community
On-prem Azure DevOps Server shops, and anyone who wants simple PAT auth with full PR lifecycle tools.
Work items (create/update/link), repositories (files, branches, commits, tree navigation), full pull-request lifecycle (create, comment, status), pipelines (run, monitor, artifacts, logs), wikis, code/wiki/work-item search, projects, users and orgs.
Self-hosted local stdio server; Node.js 16+, installed via npm. · Three methods: PAT, Azure Identity (DefaultAzureCredential), or Azure CLI login. PAT is the only method that works against on-prem Azure DevOps Server. · MIT · 384★
- Community project — not affiliated with or supported by Microsoft
- On-prem Azure DevOps Server support is PAT-only; Azure Identity and Azure CLI auth work only against cloud Services
- A fraction of the official server's adoption (384 stars vs 1,990) — smaller review surface for changes
- Community
No-code users who need work-item and build actions wired into existing Zapier automations without hosting anything.
Roughly ten documented actions: six triggers (build completed, TFVC check-ins, Git pushes, work item created/updated/commented), four write actions (queue build, create/update work items, add work-item links), plus work-item search by query syntax.
Fully hosted by Zapier at mcp.zapier.com — you get a unique server URL, nothing to install. · Managed through your Zapier account's Azure DevOps connection; Zapier stores the credential and brokers every call.
- Coverage is thin next to the official server: no repository file access, no pull-request tools, no pipeline logs, no wiki or test-plan tools — it is work-item and build-queue oriented
- Your Azure DevOps credential lives with a third party (Zapier) that sits between your agent and your org
- The MCP landing page publishes no pricing or rate limits; you find the constraints of your Zapier plan after connecting
- Closed source — no repo, stars, or commit history to verify maintenance against
- Community
Python teams that want a Python codebase to extend rather than TypeScript.
Bridges AI assistants to the Azure DevOps REST API via the Python SDK — work-item-centric, narrower than the Node.js options.
Self-hosted local server built on the Azure DevOps Python SDK. · PAT only, supplied via the AZURE_DEVOPS_PAT environment variable. · MIT · 79★
- Last pushed October 2025 — roughly ten months without a commit as of this check, so treat it as minimally maintained
- PAT-only auth: a long-lived token in an environment variable, no Entra ID option
- Small adoption at 79 stars
- Community project, unaffiliated with Microsoft
Azure DevOps MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Azure DevOps MCP Server (Microsoft official) | Microsoft | Remote: Microsoft-hosted at mcp.dev.azure.com (streamable HTTP), no install. Local: stdio via npx @azure-devops/mcp, Node.js 20+. | Remote: Microsoft Entra ID (OAuth), requires an Entra-tenant-backed organization. Local: Azure DevOps PAT or Entra ID sign-in. | MIT |
| Tiberriver256/mcp-server-azure-devops | Community | Self-hosted local stdio server; Node.js 16+, installed via npm. | Three methods: PAT, Azure Identity (DefaultAzureCredential), or Azure CLI login. PAT is the only method that works against on-prem Azure DevOps Server. | MIT |
| Zapier MCP for Azure DevOps | Community | Fully hosted by Zapier at mcp.zapier.com — you get a unique server URL, nothing to install. | Managed through your Zapier account's Azure DevOps connection; Zapier stores the credential and brokers every call. | — |
| Vortiago/mcp-azure-devops | Community | Self-hosted local server built on the Azure DevOps Python SDK. | PAT only, supplied via the AZURE_DEVOPS_PAT environment variable. | MIT |
How to choose
Pick Microsoft's official server if you're on cloud Azure DevOps Services — the remote endpoint if your client authenticates with Entra ID, the local npx server if you're on Claude Code, Claude Desktop, or Codex. Pick Tiberriver256's community server if you run on-prem Azure DevOps Server, which the official one doesn't target. Pick Zapier's hosted MCP if you want zero setup and only need work-item and build actions inside a broader Zapier automation. Pick Vortiago's Python server only if you specifically want a Python codebase to extend — it hasn't seen a push since October 2025.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Is there an official MCP server for Azure DevOps?
- Yes. Microsoft maintains microsoft/azure-devops-mcp (1,990 stars, MIT, pushed the day before we checked) and also hosts a remote endpoint at mcp.dev.azure.com so supported clients need no install at all. The local server went GA in October 2025; the remote endpoint is newer, and the repo still references its preview period.
- What does setup and authentication actually look like?
- The remote server uses Microsoft Entra ID OAuth and requires your org to be backed by an Entra tenant — standalone Microsoft-account orgs are excluded. Claude Code, Claude Desktop, and Codex can't complete that flow, so on those clients you run the local server via npx (Node.js 20+) and authenticate with a PAT or Entra sign-in. Community servers like Tiberriver256's and Vortiago's use a PAT in an environment variable.
- What if I run on-prem Azure DevOps Server instead of the cloud service?
- Microsoft's official server targets cloud-hosted Azure DevOps Services, so on-prem users should look at Tiberriver256/mcp-server-azure-devops, which documents on-prem support explicitly. Note that PAT is the only auth method that works against on-prem Server.
- Can I connect Azure DevOps to an AI agent without hosting anything?
- Two ways. Microsoft's remote endpoint at mcp.dev.azure.com requires no install if your client supports Entra ID auth. Zapier's hosted MCP requires no install with any client, but covers only around ten actions — work items and build queueing, with no repo, PR, or pipeline-log tools.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.