← Explore all mcp servers

PLANNING AND COLLABORATION / Microsoft

Azure DevOps MCP Server

Works against one named Azure DevOps organisation, and the README says to prefer the remote server when you can.

“This project gives AI agents access to Azure DevOps through the Model Context Protocol (MCP).”

01 / THE REASONING

Why this made the selection.

  • The local config passes the organisation as an argument to @azure-devops/mcp, so the tenant is not implied.
  • The README’s first note recommends the remote MCP server because it needs no local install and receives features first.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md
  • 2026-10-14 reread of retained pinned setup/configuration evidence for the specific operational details added in this batch.
  • Pinned LICENSE.md: MIT grant; previous LICENSE URL returns HTTP 404.

Our findings

  • README line recommends the Remote MCP Server instead of this local server.
  • Sample args include -y, @azure-devops/mcp and the organisation input.
  • Pinned README explicitly requires Node20+, supports domain selection and Azure CLI authentication, and recommends the separate remote option.
  • The pinned licence filename is LICENSE.md, not LICENSE. The retained Microsoft MIT text supports the unchanged source licence classification.

Not established by this review

  • The remote endpoint was not called.
  • No organisation was queried.
  • No authenticated session, installation, permission bypass or package-to-source parity test was performed.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

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

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Install Node.js 20 or newer.
  2. Replace Contoso (or {Contoso} in the JSON blocks) with the Azure DevOps organization name.
  3. Add -d with the domains you need; always include core.
  4. Complete Microsoft sign-in with an account authorized for that organization, or pass --authentication with azcli, env, envvar or pat.

Before you start

  • Node.js 20 or newer
  • An Azure DevOps organization and an account permitted to access it

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

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

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Server documentation ↗Checked

    https://github.com/microsoft/azure-devops-mcp/blob/3534051fd8af5bb0920cbfb0d5ad53a2c950a19f/README.md

    Supports: Install command and stated tools, summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  2. Repository licence ↗Checked

    https://github.com/microsoft/azure-devops-mcp/blob/3534051fd8af5bb0920cbfb0d5ad53a2c950a19f/LICENSE.md

    Supports: Redistribution terms

  3. Repository licence ↗Checked

    https://github.com/microsoft/azure-devops-mcp/blob/3534051fd8af5bb0920cbfb0d5ad53a2c950a19f/LICENSE

    Supports: Redistribution terms

Evidence & Ask