← Back to directory
A

Azure DevOps MCP Server

Official
Bring Azure DevOps projects, work items, repos, wikis, and pipelines to your AI agent
GitHub source repository ↗
★ 1.9k Stars Category · Dev Tools Very popular
64FMRS · C
Reliability
7/20
Security and permissions
12/20
Maintenance
16/20
Documentation
15/20
Setup experience
14/20

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.

Read the FMRS scoring method →

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.

Tools

The tool list has not been reviewed yet.

Setup

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.

claude_desktop_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}"]
    }
  }
}

Fit and risk

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

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

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

Visual Studio CodeFull support