Azure DevOps MCP Server
Microsoft's MCP server for Azure DevOps work items, repos, pipelines and more, hosted or local.
Sources and review
Checked against public documentation on . Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.
Teams on Azure DevOps who want agents to triage work items and review pull requests.
About Azure DevOps MCP Server
Microsoft's Azure DevOps MCP Server gives AI agents access to Azure DevOps work items, repositories, pipelines, wikis, test plans, search and Advanced Security. Microsoft recommends the hosted remote server, which needs no installation and receives features first; a local stdio server is available as an npm package, with domains to load only the tool groups you need. A recent consolidation renamed many tools.
Azure DevOps MCP Server is listed in this index written primarily in TypeScript, with 2.1k stars on GitHub. Its latest recorded repository push was in October 2026; that is not an ASE editorial review date.
Before connecting: access and data
This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.
- List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
- Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
- Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
- Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.
Add Azure DevOps MCP Server to your MCP client
A hosted server: point your client at its URL and complete its sign-in there. In Claude Desktop or claude.ai, add it under Settings → Connectors → Add custom connector instead. Replace <your-organization> with your own value first.
Claude Code
claude mcp add --transport http azure-devops-mcp 'https://mcp.dev.azure.com/<your-organization>'Cursor
{
"mcpServers": {
"azure-devops-mcp": {
"url": "https://mcp.dev.azure.com/<your-organization>"
}
}
}VS Code
{
"servers": {
"azure-devops-mcp": {
"type": "http",
"url": "https://mcp.dev.azure.com/<your-organization>"
}
}
}Codex
codex mcp add azure-devops-mcp --url 'https://mcp.dev.azure.com/<your-organization>'