# Azure DevOps

> Drive Azure DevOps repos, pull requests, work items, and pipelines from an AI agent — Microsoft official.

[Canonical HTML page](https://top-mcps.com/mcp/azure-devops) · [server.json](https://top-mcps.com/mcp/azure-devops.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

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

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
claude mcp add azure-devops -- npx -y @azure-devops/mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

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

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

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

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

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

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

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

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@azure-devops/mcp"
          ]
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.azure-devops]
command = "npx"
args = [
  "-y",
  "@azure-devops/mcp",
]
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "azure-devops": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@azure-devops/mcp"
        ]
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

Azure DevOps doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

```none

```

## At a glance

- **Maintainer:** Microsoft
- **Transport:** stdio, Streamable HTTP
- **Auth model:** OAuth 2.1
- **Required secrets:** None
- **Supported clients:** Claude, Cursor, VS Code, GitHub Copilot, Any MCP-compatible client
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-07-16
- **GitHub stars:** 1,894 (fetched 2026-07-17T12:42:37.535Z)
- **Score:** 87/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/microsoft/azure-devops-mcp

## Quick answer

**What it does.** Exposes Azure DevOps operations as MCP tools: repos + pull requests, work items + iterations, builds + pipelines, test plans, and wiki pages, over stdio or a remote HTTP server.

**Best for:**
- Pull-request review + creation in ADO
- Work-item triage and updates
- Pipeline and build status queries
- Test-plan inspection
- az login auth (no stored PAT)

**Not for:**
- GitHub or GitLab repos
- Orgs not on Azure DevOps
- Environments without Azure CLI available

## Description

Microsoft's official Azure DevOps MCP (MIT, ~1.9k stars) is a thin abstraction over the Azure DevOps REST APIs: repositories and pull requests, work items and iterations, builds and pipelines, test plans, and wiki. It authenticates through your Microsoft account / Azure CLI login rather than a stored PAT.

## Why it matters

Azure DevOps is the system of record for a large share of enterprise engineering orgs. A first-party MCP lets an agent triage work items, review PRs, and read pipeline status without leaving the model.

## Key features

- Repos + pull requests + work items + pipelines + wiki
- az login auth via Azure Identity
- Local stdio or remote HTTP server
- Thin, purpose-specific tools over the ADO REST API
- Official Microsoft, MIT, Node.js 20+

## FAQ

### How does it authenticate?

Through your Microsoft account via Azure CLI (`az login`) / Azure Identity — a browser prompt on first run. No personal access token is stored in the config.

### Local or remote?

Both. Run it locally over stdio with `npx -y @azure-devops/mcp`, or connect to the recommended remote HTTP server.

### Does it work with GitHub?

No — this is Azure DevOps specific. For GitHub use the GitHub MCP; for GitLab use the GitLab MCP.

## Changelog

- **2026-07-16** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-06-01** — Initial directory listing.