Azure DevOps MCP

What it does

Exposes Azure DevOps to an agent: work items, repositories, pull requests, and pipelines. The practical use is triage — reading a failing build and the work item it belongs to without tab-hopping. Authentication goes through an Azure identity, so an agent inherits whatever access your account already has. Scope it to one project before you point it at an organisation.

Install

npx -y @azure-devops/mcp

Client configuration

Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.

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

When to use it

Reach for this when the task needs azure inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.

Other TypeScript servers

• Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
• Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
• Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude