Official Microsoft server · reviewed August 17, 2026

Azure DevOps MCP Server

This page is for people who searched Azure DevOps and landed on an MCP install result. The official server is @azure-devops/mcp. Microsoft now recommends the remote endpoint first. The local npx package stays for stdio clients.

Source-checked against the official microsoft/azure-devops-mcp README, npm @azure-devops/[email protected], and Microsoft Learn remote-server docs.

Start here

Remote MCP

Use https://mcp.dev.azure.com/{organization} when the client supports HTTP MCP. Official docs say this path gets new features first.

Only if needed

Local stdio

Use npx -y @azure-devops/mcp <org> when the client cannot call the remote server and needs a local process.

Do not confuse

Azure cloud MCP

Blob Storage, Functions, and Cosmos DB belong on Azure MCP, not this Azure DevOps server.

What this page is, and what it is not

Searchers hitting this URL often want Azure Boards, Repos, Pipelines, or a generic Azure DevOps overview. AgentSkillsHub ranks here because Microsoft published an official MCP server for that product. This page answers the install contract: remote versus local, organization name, identity, domains, and the recent tool rename. It does not replace Azure DevOps documentation for boards, billing, or organization admin.

If the job is cloud infrastructure rather than the DevOps product, open Azure MCP. If the job is Git history on a local clone, use mcp-server-git.

Recommended remote setup

{
  "servers": {
    "ado-remote-mcp": {
      "url": "https://mcp.dev.azure.com/{organization}",
      "type": "http"
    }
  },
  "inputs": []
}

Official recommended path. Replace {organization} and start the server from the MCP view, then try List ADO projects.

Local VS Code / Copilot stdio

{
  "inputs": [
    {
      "id": "ado_org",
      "type": "promptString",
      "description": "Azure DevOps organization name (e.g. 'contoso')"
    }
  ],
  "servers": {
    "ado": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@azure-devops/mcp", "${input:ado_org}"]
    }
  }
}

Use this only when the client needs a local process. Node.js 20+ is required.

Local domain filter

{
  "inputs": [
    {
      "id": "ado_org",
      "type": "promptString",
      "description": "Azure DevOps organization name (e.g. 'contoso')"
    }
  ],
  "servers": {
    "ado_with_filtered_domains": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@azure-devops/mcp",
        "${input:ado_org}",
        "-d",
        "core",
        "work",
        "work-items"
      ]
    }
  }
}

Always keep core. Add work and work-items only when the agent should touch boards.

Claude Code

claude mcp add --transport stdio azure-devops -- npx -y @azure-devops/mcp Contoso

Replace Contoso, then run claude mcp list to confirm the server is visible.

Cursor project config

{
  "mcpServers": {
    "ado": {
      "command": "npx",
      "args": ["-y", "@azure-devops/mcp", "Contoso"]
    }
  }
}

Save as .cursor/mcp.json, enable the ado server in Cursor Settings, then test in Agent chat.

Windows desktop wrapper

{
  "mcpServers": {
    "azure-devops": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@azure-devops/mcp", "Contoso"]
    }
  }
}

Use cmd /c when a Windows desktop client cannot launch npx from its own PATH.

Temporary pin after tool rename

npx -y @azure-devops/[email protected] Contoso

Official README: pin 2.8.1 only if renamed tools break an existing agent or skill.

Authentication and identity

Interactive Microsoft sign-in is the local default. Other methods are explicit flags. Official getting-started docs say not to commit tokens into the MCP JSON file.

Method	Flag	Required setup
Interactive	default	Microsoft account sign-in in a browser. Omit --authentication.
Azure CLI	--authentication azcli	Requires an active az login session on the same machine.
Azure credential chain	--authentication env	Uses DefaultAzureCredential from the process environment.
Bearer token	--authentication envvar	Reads ADO_MCP_AUTH_TOKEN. Do not put the token in the JSON file.
Personal Access Token	--authentication pat	PERSONAL_ACCESS_TOKEN must be base64 of email:pat. Official docs require this encoding.

Local domains

core

Project and organization lookup. Always include this domain.

work / work-items

Iterations, teams, and work-item read or write tools.

repositories

Azure Repos listing and repository inspection.

pipelines

Build and pipeline status for the selected organization.

wiki / test-plans / search / advanced-security

Load only when that workflow is in scope.

Worked first tasks

Prove the connection

After sign-in, ask the client to list Azure DevOps projects. If the list is empty, the organization name or identity is wrong. Do not continue to write tools.

Read the current sprint

Load core, work, and work-items. Ask for work items in the current iteration for one project and one team. Keep the first pass read-only.

Inspect one pipeline

Add the pipelines domain only when needed. Ask for recent builds for one project. Treat queue or cancel actions as a second, reviewed step.

Common errors

Login fails with a personal Microsoft account.

Likely cause: Official FAQ says personal accounts are not supported.

Fix: Switch to an Entra ID-backed work or school account that can open the Azure DevOps organization.

The agent cannot find a renamed tool.

Likely cause: Microsoft consolidated and renamed tools after 2.8.1.

Fix: Read TOOLSET.md, update prompts, or temporarily pin @azure-devops/[email protected].

The client shows too many tools or hits a tool-limit error.

Likely cause: The local server loaded every domain.

Fix: Add -d core plus only the needed groups, then restart the client.

npx works in a terminal but not in the desktop app.

Likely cause: The app inherited a different PATH, or Windows needs cmd /c.

Fix: Use the Windows wrapper, or give the client the full npx path.

Official sources: Microsoft Learn remote server, local getting started, TOOLSET.md.

Frequently asked questions

What is the Azure DevOps MCP Server?

It is the official Microsoft MCP server for Azure DevOps. An MCP client can list projects, inspect work items, repositories, pipelines, wikis, and test plans through Azure DevOps APIs. It is not the Azure cloud MCP server for Blob Storage or Cosmos DB.

Should I use the remote or local Azure DevOps MCP server?

Official docs now recommend the remote server at https://mcp.dev.azure.com/{organization}. It needs no local package install. Use the local @azure-devops/mcp package only when a client requires stdio.

What is the local install command?

npx -y @azure-devops/mcp <organization>. Replace the organization with the Azure DevOps org name, such as Contoso, not the full https://dev.azure.com URL.

Do personal Microsoft accounts work?

No. Official FAQ states personal accounts are not supported. The account must be backed by Microsoft Entra ID. A personal-account login error means the wrong identity type is being used.

Why did Azure DevOps MCP tool names change?

Microsoft completed a tool consolidation and renamed existing tools. Check TOOLSET.md for current names. If a skill or agent still depends on old names, official docs say you can temporarily pin @azure-devops/[email protected].

Which domains should I load on the local server?

Available domains are core, work, work-items, search, test-plans, repositories, wiki, pipelines, and advanced-security. Always include core. Load only the groups the client actually needs.

Is Azure DevOps MCP the same as Azure MCP?

No. Azure DevOps MCP talks to boards, repos, pipelines, wikis, and test plans. Azure MCP talks to Azure cloud services such as Blob Storage, Functions, and Cosmos DB. Use the matching server for the job.