Overview
What Azure DevOps MCP Server does
Azure DevOps MCP gives agents focused tools over Azure DevOps REST capabilities. Microsoft's hosted streamable-HTTP service is the recommended direction and removes the local Node.js process for supported clients, while the generally available npm server remains an option for local workflows. The local server can limit its large surface through named domains such as work items, repositories, pipelines, wiki, and advanced security.
Best for
- Reviewing work items, pull requests, and build state from an editor
- Creating and maintaining Azure DevOps wiki and planning content
- Agent workflows that need a thin, explicit layer over Azure DevOps APIs
Not ideal for
- Remote MCP clients that are not yet supported by the Entra preview
- On-premises Azure DevOps Server without validating compatibility
- Loading every tool domain when the agent needs only one workflow area
Capabilities
What an agent can do
- 01
Projects, teams, iterations, and work items
- 02
Azure Repos and pull-request operations
- 03
Pipeline and build inspection
- 04
Wiki page creation and updates
- 05
Test plan and code search
- 06
Advanced Security alerts and domain-level tool selection
Representative tools and operations
core_list_projectswit_list_my_work_itemsrepo_list_repos_by_projectrepo_list_pull_requests_by_repopipelines_get_buildswiki_get_wikiswiki_create_pagesearch_code
Installation
Connect Azure DevOps MCP Server
Use the publisher’s current instructions as the source of truth. The examples below were checked on .
VS CodeUse the recommended hosted endpoint
https://mcp.dev.azure.com/{organization}{"servers":{"ado-remote-mcp":{"url":"https://mcp.dev.azure.com/{organization}","type":"http"}},"inputs":[]}Generic local clientLaunch the npm server over stdio
npx -y @azure-devops/mcp YOUR_ORGANIZATIONUse -d core work work-items to expose a smaller planning-focused toolset; supply the documented authentication option for the environment.Trust and access
Authentication and security notes
Authentication: The hosted preview uses Microsoft Entra ID and requires the Azure DevOps organization to be connected to Entra. The local server supports interactive Entra authentication and Azure DevOps personal access token options.
Review before connecting
- Use Azure DevOps permissions and project membership as the primary access boundary.
- For the local server, enable only the domains required for the agent's assignment.
- Review write operations affecting work items, repositories, pipelines, and wiki pages.
- Keep PATs out of repository files and prefer interactive Entra authentication where it fits the client.
Known limitations
- The hosted server remains in public preview and can change before general availability.
- Remote support is currently narrower than local-client support because some clients require Entra dynamic registration.
- The local server requires Node.js 20 or newer.
- A full domain set exposes many tools and may exceed or confuse client tool-selection limits.
Evidence
Sources used for this guide
Facts were checked against primary publisher material. Descriptions and guidance are original Graphify summaries.
FAQ
Questions about Azure DevOps MCP Server
Should I choose the hosted or local Azure DevOps server?
Use the hosted service when your organization and client meet the preview requirements. Keep the local npm server for unsupported clients, local control, or workflows that require its authentication options.
Can the Azure DevOps tool list be reduced?
Yes for the local server. Pass domain names such as core, work-items, repositories, wiki, or pipelines so the agent loads only relevant tools.
