Azure DevOps MCP Server for Claude

Content

The Azure DevOps MCP Server brings Azure DevOps context into AI-assisted development workflows. It gives agents structured access to project metadata, work items, repositories, pull requests, branches, files, pipeline runs, build logs, artifacts, wikis, test plans, and search results so a task can start from the actual Azure DevOps source of truth rather than a copied ticket or stale summary.

Microsoft now recommends the Azure DevOps-hosted remote MCP server for supported clients. The remote server uses streamable HTTP at https://mcp.dev.azure.com/{organization}, authenticates with Microsoft Entra ID, and can be narrowed with toolset and read-only headers. The local @azure-devops/mcp package remains useful for Claude Code, Cursor, Codex, and other stdio-oriented clients while remote OAuth client support continues to roll out.

Features

• Remote HTTP endpoint at https://mcp.dev.azure.com/{organization} for the public preview hosted server.
• Local stdio server through npx -y @azure-devops/mcp.
• Core organization, project, and team discovery.
• Work item lookup, batch retrieval, comments, revisions, backlog data, saved query results, and full-text work item search.
• Repository, branch, file, commit, pull request, and pull request thread inspection.
• Pipeline build listing, build status, build changes, logs, pipeline runs, and artifacts.
• Wiki listing, page retrieval, and wiki search.
• Test plan, suite, case, and build test-result lookup.
• Remote toolset filtering with X-MCP-Toolsets and read-only restriction with X-MCP-Readonly.
• Local domain filtering for focused tool loading, such as core, work, work-items, repositories, wiki, pipelines, and test-plans.

Use Cases

• Ask Claude to list your assigned Azure DevOps work items and summarize what needs attention.
• Pull a work item, related PRs, and repository files before implementing a feature.
• Review pull request threads and changed branches before drafting a response.
• Inspect a failed build's status, associated commits, work items, and logs.
• Search Azure DevOps wiki pages for runbooks or architecture notes connected to a task.
• Limit the server to issue-tracking toolsets for triage workflows that should not touch repositories or pipelines.

Installation

Claude Code with the local stdio server

1. Confirm Node.js 20 or later and npx are available.
2. Confirm your Azure DevOps organization name, project, and authentication method.
3. Add the local MCP server:

claude mcp add azure-devops -- npx -y @azure-devops/mcp YOUR_AZURE_DEVOPS_ORG

1. Use domain filters when you only need a subset of tools:

claude mcp add azure-devops -- npx -y @azure-devops/mcp YOUR_AZURE_DEVOPS_ORG -d core work work-items repositories

1. Authenticate when the server prompts, then test with a read-only request such as listing projects or your assigned work items.

Remote MCP server in Visual Studio Code

1. Confirm the Azure DevOps organization is connected to Microsoft Entra ID.
2. Add an MCP configuration like the one below to .vscode/mcp.json.
3. Start the MCP server from the VS Code MCP view.
4. Authenticate with the Microsoft Entra account that has access to the Azure DevOps organization.
5. Ask a read-only prompt such as List the projects in my Azure DevOps organization.

Configuration

Remote read-only toolset configuration

{
  "servers": {
    "ado-remote-mcp": {
      "url": "https://mcp.dev.azure.com/YOUR_AZURE_DEVOPS_ORG",
      "type": "http",
      "headers": {
        "X-MCP-Toolsets": "repos,wiki,wit",
        "X-MCP-Readonly": "true"
      }
    }
  },
  "inputs": []
}

Local stdio configuration

{
  "mcpServers": {
    "azure-devops": {
      "command": "npx",
      "args": [
        "-y",
        "@azure-devops/mcp",
        "YOUR_AZURE_DEVOPS_ORG",
        "-d",
        "core",
        "work",
        "work-items",
        "repositories"
      ],
      "env": {
        "ado_mcp_project": "YOUR_PROJECT"
      }
    }
  }
}

Examples

Triage assigned work items

List my Azure DevOps work items in PROJECT_NAME and group them by priority, blocked status, and next action.

Inspect a pull request

Find pull requests in PROJECT_NAME that require my review, summarize the active comment threads, and do not post any comments.

Debug a failed pipeline

Get the latest failed pipeline run for PROJECT_NAME, summarize the failed stage and relevant logs, and link related commits or work items.

Read a wiki runbook

Search Azure DevOps wiki pages for the deployment rollback runbook and summarize the exact steps without changing the wiki.

Source notes

• Microsoft Learn documents the remote Azure DevOps MCP Server as a public preview hosted service using streamable HTTP transport at https://mcp.dev.azure.com/{organization}.
• The remote setup guide says the hosted server avoids local installation, authenticates with Microsoft Entra ID, and provides access to work items, pull requests, pipelines, and more.
• Microsoft documents toolset filtering with X-MCP-Toolsets, read-only filtering with X-MCP-Readonly, individual tool selection with X-MCP-Tools, and insiders features with X-MCP-Insiders.
• The available remote toolsets include repos, wit, pipelines, wiki, work, and testplan, with read-only and write-capable tools called out in the Microsoft Learn reference.
• The official GitHub repository recommends the remote MCP server going forward while continuing to support the local @azure-devops/mcp stdio package for clients and scenarios that need it.
• npm metadata identifies @azure-devops/mcp as Microsoft's MCP server for interacting with Azure DevOps and points to the microsoft/azure-devops-mcp repository under the MIT license.

Duplicate check

Checked current content/mcp/, content/tools/, guides, skills, agents, open pull requests, and repository-wide content for Azure DevOps, azure-devops-mcp, microsoft/azure-devops-mcp, @azure-devops/mcp, mcp.dev.azure.com, ado-remote-mcp, work item, pull request tools, Microsoft Entra, pipelines, and issue tracker MCP. Existing Jira MCP content covers Atlassian Jira and Confluence, while this entry covers Microsoft Azure DevOps work items, repos, PRs, pipelines, wiki, and test plans. Existing Microsoft AutoGen content is an agent framework entry, not an Azure DevOps MCP server. No dedicated Azure DevOps MCP entry, Azure DevOps source URL duplicate, or open duplicate PR was found.

Disclosure

Editorial listing. No paid placement or affiliate link is used.