Azure DevOps MCP server
Azure DevOps MCP Server
Official Microsoft MCP server for Azure DevOps: work items, repositories, builds, test plans, and wiki from the agent
- 2,075 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Can create and modify work items and wiki pages
- Acts on behalf of an account with access to code and pipelines
Install
- Works in
Manual install
{
"servers": {
"ado-remote-mcp": {
"url": "https://mcp.dev.azure.com/{organization}",
"type": "http"
}
},
"inputs": []
}Remote server is the recommended option. Replace {organization} with your organization name.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can create and modify work items and wiki pages
- Acts on behalf of an account with access to code and pipelines
This is third-party code. Review the repository files before installing.
What it does
The server provides the agent access to the Azure DevOps REST API through a set of focused tools: projects, teams, iterations, work items, repositories, pipelines, test plans, wiki, and search. The agent can read, create, and update data, such as wiki pages. Tools are divided into domains, and the -d flag allows loading only the needed groups. Microsoft recommends the remote server; the local one via npx is kept for stdio scenarios.
Who it is for. For teams managing work items, code, and builds in Azure DevOps who want to work with them from the agent.
Good fit when
- Need to get a list of your tasks in the current iteration
- Need to view builds, repositories, or test plans of a project
- Need to create or update a project wiki page
Not a fit when
- Team works in GitHub, GitLab, or Jira
- No access to an Azure DevOps organization
Example request
Show my work items in the current iteration of the Contoso projectMCP
- Transport
- stdio, http
- Authentication
- OAuth
Environment variables
ADO_MCP_AUTH_TOKENsecret- Bearer token for --authentication envvar mode
PERSONAL_ACCESS_TOKENsecret- Base64 of the string email:PAT for --authentication pat mode
ado_mcp_project- Default project
ado_mcp_team- Default team
Limitations
Requires an Azure DevOps organization and a Microsoft account with access. The local server requires Node.js 20; after consolidation, tools were renamed and old agents may break. Availability of Microsoft services from Russia without VPN is not guaranteed.
How to disable. Remove the ado server from .vscode/mcp.json or your MCP client configuration.
FAQ
What authorization methods are available for the local server?
Interactive login by default, Azure CLI token, Azure credential chain, bearer token from ADO_MCP_AUTH_TOKEN, and personal access token.
Why domains?
There are many tools, and some clients limit their number. Domains load only the needed groups; always include core.
Discussion
No questions or reviews yet.
Related
MCP serversMicrosoft's official MCP server for Azure: the agent sees subscription resources and works with Azure services on your behalf
Azure Skills
Azure Skills Plugin
Microsoft's official plugin: Azure skills plus the Azure MCP Server and Foundry MCP wired in for real cloud actions
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
The remote MCP server of Devopness, a platform that builds infrastructure and deploys apps in your own cloud accounts
Official Cloudflare MCP server: the agent drives the whole Cloudflare API by searching the spec and running code
Datadog's official managed MCP server: logs, metrics, traces and incidents right in your agent
README in short
The README advises starting with the Microsoft remote server and shows configuration for VS Code. Local installation is described via npx and .vscode/mcp.json; separate guides exist for other clients: Visual Studio, Codex, Claude Code, Cursor, OpenCode. Tool domains and the project with default team are explained. MIT license.