← Back to directory
A

Azure DevOps MCP Server

Official
Bring Azure DevOps projects, work items, repos, wikis, and pipelines to your AI agent
Category
Dev Tools #60 of 438
Stars
★ 2.1k Very popular
Transport
stdio (local process) · Streamable HTTP
Runtime
Node.js 20+ · Hosted (no local runtime)
Credentials
API key / credential required
License
MIT
Last commit
64FMRS · C

An official Microsoft-maintained Azure DevOps MCP server offering both a recommended remote endpoint and an optional local server, covering projects, work items, repos, wikis, test plans, and pipelines; requires Microsoft account sign-in, has a large tool surface best scoped via domains, and recently underwent a breaking tool renaming worth checking before upgrading.

Strongest · Maintenance 16/20 Weakest · Reliability 7/20

Reliability
7/20
Security and permissions
12/20
Maintenance
16/20
Documentation
15/20
Setup experience
14/20
Why each score
Reliability 7/20
No test files, CI workflows, or source code are present in the evidence, so the MCP init/tool-list handshake cannot be verified as reproducible; per the static calibration rule reliability is capped at 12. More concerning, the manifest declares the npm package identifier as '@microsoft/azure-devops' while every install example in the README uses 'npx -y @azure-devops/mcp' / '@azure-devops/[email protected]' — a direct mismatch between the server.json manifest and the actual documented package, suggesting the manifest may be stale or inaccurate. The README also carries a prominent warning about a recent breaking 'tool consolidation and renaming', indicating recent instability. Combined, this warrants a low score of 7.
Security and permissions 12/20
The remote server authenticates via Microsoft account OAuth in-browser, and the local server supports azcli-based authentication; no hardcoded secrets or tokens appear in install examples, so no red line is triggered. However, the tool surface is broad (work-items, repositories, wiki, pipelines, advanced-security domains), includes write operations (creating/updating wiki pages), and the 'advanced-security' domain likely touches sensitive security-scan data — yet the documentation provides no explicit confirmation step, least-privilege scoping, or data-boundary disclosure for these write/sensitive paths; Domains only provide coarse tool-set filtering, not read/write separation. Main risks are visible but mitigations are incompletely documented, so 12 is appropriate.
Maintenance 16/20
The repository is maintained by Microsoft's official GitHub org under the MIT license, with 1942 stars and only 12 open issues, suggesting reasonably responsive issue handling. The README references nightly builds (@next) and version pinning (e.g., 2.8.1), indicating an active release cadence, and CONTRIBUTING.md plus a Code of Conduct establish governance. However, no explicit SECURITY.md or vulnerability-reporting channel is evidenced in the provided material, so it falls short of full marks: 16.
Documentation 15/20
Documentation is well-layered, spanning TOOLSET.md, GETTINGSTARTED.md, TROUBLESHOOTING.md, EXAMPLES.md, HOWTO.md, and FAQ.md, with multi-client configuration examples (VS Code, Visual Studio 2022, Codex, Claude Code, Cursor, etc.) and GIF walkthroughs. However, it does not disclose API rate limits, quota, or cost considerations, and the manifest's package name conflicts with the README's install command — an unresolved discrepancy that counts as a hidden inconsistency. This caps the score at 15.
Setup experience 14/20
The remote server requires only a single URL entry in mcp.json — near-zero installation friction — while the local server needs just one npx command plus an input parameter, with optional Domains and project/team defaults for finer control, all backed by clear step-by-step client configuration examples. Since this is a purely static review with no verifiable execution evidence (no CI or committed tests proving these steps actually work end-to-end), the static calibration rule caps setup at 15, so it is scored 14.

Static review · not runListed 2026-08-06

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • Teams already using Azure DevOps for work items, repos, wikis, or pipelines
  • Developers using VS Code with GitHub Copilot (or another MCP-capable client)
  • Scenarios wanting natural-language access to Azure DevOps without hand-writing REST API calls

Not for

  • Teams not using Azure DevOps, or relying solely on GitHub or other project-management tools
  • Users wanting a minimal, zero-configuration server with no domain selection or account sign-in
  • Scenarios highly sensitive to breaking changes during preview — the README notes a recent full tool renaming/consolidation

Required permissions

  • Requires OAuth browser sign-in with a Microsoft account matching the target Azure DevOps organization (remote and local)
  • Local server also supports authentication via --authentication azcli
  • Requires an Azure DevOps organization identifier (e.g. 'contoso')
  • Local mode can set default project and team via environment variables to skip selection prompts

Risks and side effects

  • Broad tool surface may allow modifying organizational data such as wiki pages and work items — verify the signed-in account's permission scope
  • The remote server is in preview, with functionality and issue tracking still evolving
  • A recent full tool consolidation renamed existing tools, which can break existing agents/skills unless pinned to an older version or updated per docs/TOOLSET.md
  • The local server requires Node.js 20+; an unmet version requirement will cause install or runtime failures

Setup

Before you start

Runtime:Node.js 20+ · Hosted (no local runtime)

Recommended (remote, no install): add an entry to .vscode/mcp.json with type 'http' pointing to https://mcp.dev.azure.com/{organization}, then start it from the MCP view in VS Code. The first tool call opens a browser prompt to sign in with a Microsoft account matching the chosen organization.
Optional (local stdio): install Node.js 20+, configure .vscode/mcp.json with command 'npx' and args ["-y", "@azure-devops/mcp", "${input:ado_org}"] as a stdio server, save and start it in VS Code, then select tools in Agent Mode. Use the -d flag (e.g. "-d", "core", "work", "work-items") to load only needed tool domains; keep the core domain enabled.

MCP config · JSON
{
  "inputs": [
    {
      "id": "ado_org",
      "type": "promptString",
      "description": "Azure DevOps organization name (e.g. 'contoso')"
    }
  ],
  "servers": {
    "ado": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@azure-devops/mcp", "${input:ado_org}"]
    }
  }
}

Works in clients that read an "mcpServers" key. For clients such as VS Code that use a different key, the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "ado": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@azure-devops/mcp",
        "${input:ado_org}"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add ado -- npx -y @azure-devops/mcp '${input:ado_org}'

Run it in a terminal; replace any <…> placeholders with your own values first.

Check that it works

Save .vscode/mcp., start the server from the MCP view in VS Code, and run the prompt 'List ADO projects' in Copilot Chat Agent Mode; the first ADO tool call opens a browser for Microsoft account login, and a returned project list confirms the connection.

Troubleshooting

  1. Verify the organization identifier in mcp.json is correct and matches the signed-in account's organization
  2. Watch for the browser sign-in prompt on first tool use and ensure the Microsoft account matches the selected organization
  3. In local mode, confirm the needed tool domains are enabled via -d; core information depends on the core domain
  4. If tools are missing or behave unexpectedly, check whether the recent tool renaming is the cause — see docs/TOOLSET.md or pin to @azure-devops/[email protected]
  5. Consult docs/TROUBLESHOOTING.md and docs/FAQ.md in the repository for common issue resolution steps

Things to try

Once connected, you can ask your AI assistant things like:

  • List my ADO projects
  • List ADO Builds for 'Contoso'
  • List work items in current iteration for 'Contoso' project and 'Contoso Team'
  • Get the content of the wiki page '/API/Authentication' from the Documentation wiki

Use cases

List my Azure DevOps projects
List builds, repositories, or test plans for a given project
List teams and iterations for a project
List my or the team's work items in the current iteration
List, create, or update project wiki pages and fetch their content

Supported clients

VS Code

Listed from the project's documentation, not tested by this site.

Overview

Official Microsoft-maintained MCP server that connects AI agents to Azure DevOps, exposing organizations, projects, boards/work items, repositories, wikis, test plans, and pipelines. The recommended path is a no-install remote streamable-HTTP endpoint (mcp.dev.azure.com/{organization}); an optional local Node.js/npm stdio server is also provided, with tool coverage scopeable via 'domains' such as core, work, work-items, search, test-plans, repositories, wiki, pipelines, and advanced-security.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 64.1k · Tools 2 Compare with this →

Source revision 7f2a6b9fae78 Data synced 2026-11-04 Read the FMRS scoring method