Azure DevOps MCP Server
Microsoft's official MCP server for Azure DevOps: work items, repos, builds, test plans and wikis from your agent
Install
{
"servers": {
"ado-remote-mcp": {
"url": "https://mcp.dev.azure.com/{organization}",
"type": "http"
}
},
"inputs": []
}Hosted remote server, the recommended option. Replace {organization} with your organization name.
This is third-party code. Review the repository files before installing.
What it does
The server exposes the Azure DevOps REST API to the agent through focused tools: projects, teams, iterations, work items, repos, pipelines, test plans, wikis and search. The agent can write as well as read, for example create and update wiki pages. Tools are grouped into domains, and the -d flag loads only the groups you need. Microsoft recommends the hosted remote server; the local npx server remains for stdio setups.
Who it is for. For teams that track work, code and builds in Azure DevOps and want to use them from an agent.
Good fit when
- You need your work items for the current iteration
- You need to review builds, repos or test plans of a project
- You need to create or update a project wiki page
Not a fit when
- Your team uses GitHub, GitLab or Jira instead
- You have no access to an Azure DevOps organization
Example request
List my work items in the current iteration of the Contoso projectLimitations
Requires an Azure DevOps organization and a Microsoft account with access. The local server needs Node.js 20; a recent tool consolidation renamed tools and may break older agent setups. Access to Microsoft services from Russia without a VPN is not guaranteed.
How to disable. Remove the ado server from .vscode/mcp.json or your MCP client config.
MCP
- Transport
- stdio, http
- Authentication
- OAuth
| Environment variables | |
|---|---|
| ADO_MCP_AUTH_TOKEN secret | Bearer token for --authentication envvar |
| PERSONAL_ACCESS_TOKEN secret | Base64 of email:PAT for --authentication pat |
| ado_mcp_project | Default project |
| ado_mcp_team | Default team |
Security check
- Can create and modify work items and wiki pages
- Acts on behalf of an account with access to code and pipelines
README in short
The README recommends starting with Microsoft's hosted server and shows the VS Code configuration. Local install uses npx and .vscode/mcp.json, with a separate guide for Visual Studio, Codex, Claude Code, Cursor and OpenCode. It covers tool domains and default project and team settings. MIT licensed.
FAQ
Which auth methods does the local server support?
Interactive sign-in by default, Azure CLI token, Azure credential chain, a bearer token from ADO_MCP_AUTH_TOKEN, and a personal access token.
Why domains?
There are many tools and some clients cap their number. Domains load only the groups you need; always include core.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring
A GitHub Action that runs Claude Code in pull requests and issues: answers mentions, reviews and makes changes