Azure DevOps MCP Server: Work Items, Repos and Pipelines
Microsoft's Azure DevOps MCP server lets Claude read work items, repos, builds, wikis and test plans. Claude Code command, remote vs local server, caveats.
By Claudekit Team Published 2 min read
- Type
- MCP Server
- Pricing
- Open Source
- Repository
- github.com
- GitHub stars
- 2,067
- Website
- learn.microsoft.com
The Azure DevOps MCP Server is Microsoft’s official Model Context Protocol server for Azure DevOps. It lets Claude list projects, work items, iterations, repos, builds, pipelines, test plans and wikis, and create or update items such as wiki pages. Each tool is a thin layer over the Azure DevOps REST API, and Claude does the reasoning on top.
Who it is for
Teams that plan and ship in Azure DevOps and want Claude Code to read the current sprint, pick up a work item, or check a failing build without opening the portal.
Install
The repo’s getting-started guide gives this Claude Code command for the local server. Replace {organization} with your organization name:
claude mcp add --transport stdio azure-devops -- npx -y @azure-devops/mcp {organization}Check it with claude mcp list. A browser window opens for Microsoft sign-in on first use. You need Node.js 20 or later. To load fewer tools, add domains after the organization, for example -d core work work-items.
Microsoft also runs a hosted remote server at https://mcp.dev.azure.com/{organization}. Its docs say Claude Code needs a custom Microsoft Entra app registration to authenticate to it, and the organization must be backed by an Entra tenant.
Use cases
- Sprint view: “List my work items in the current iteration for the Contoso project.”
- Build checks: list recent builds and ask why one failed.
- Wiki upkeep: create or update a wiki page from your code changes.
- Code context: list repos and pull requests related to a work item.
Pros
- Official, MIT licensed and maintained by Microsoft.
- Domain filtering keeps the tool list small.
- Several auth options, including Azure CLI and PATs for headless setups.
- The remote server supports a read-only header.
Cons and caveats
- The remote server, which Microsoft recommends, needs extra Entra setup for Claude Code.
- Microsoft says the remote server will eventually replace the local one, so plan for a migration.
- A PAT grants real access. Scope it narrowly and keep it in an environment variable.
Links
- Repo: microsoft/azure-devops-mcp
- Docs: Azure DevOps remote MCP server
- Package: @azure-devops/mcp on npm
- Related: Azure MCP Server, GitHub MCP server, Linear MCP
Checked 24 Oct 2026 against the vendor repo and the Microsoft Learn docs.
Frequently asked questions
Should I use the remote or the local server?
Microsoft recommends the remote server, which needs no install and gets features first. But Claude Code needs a custom Microsoft Entra app registration to authenticate to it, so the local server is simpler for many Claude Code users.
How do I limit which tools load?
On the local server, pass -d with domains such as core, work-items, repositories, wiki or pipelines. Always include core. Without -d, all domains load.
Which sign-in methods does the local server support?
Interactive browser sign-in by default, plus azcli, env, envvar (ADO_MCP_AUTH_TOKEN) and pat (PERSONAL_ACCESS_TOKEN) via --authentication.
Is there a read-only mode?
On the remote server, yes. Send the X-MCP-Readonly header to restrict it to read-only operations.