azdo-mcp

An MCP server that connects Claude to Azure DevOps: give Claude a work item or pull request number and it can read it, find related work, comment, update fields and open pull requests.

It runs locally over stdio and works with Claude Code, Claude Desktop and any other MCP client.

> What is bug 4821 about, and is anyone working on it?
> List my active work items in the current sprint.
> Review PR 312 and leave comments on anything risky.
> Create a task under story 4790 for the Safari login fix and assign it to me.

Tools

Work items

Repositories and pull requests

✏️ tools change data. They are not registered at all in read-only mode.

Related MCP server: ado-mcp

Setup

You need Node.js 20 or later and either a Personal Access Token or the Azure CLI.

1. Credentials

Personal Access Token (PAT). In Azure DevOps open User settings → Personal access tokens → New token and grant:

Azure CLI. If AZURE_DEVOPS_PAT is not set, the server asks the Azure CLI for a token, so az login with an account that has access to the organization is all you need.

2. Add the server to Claude

Claude Code

claude mcp add azure-devops --scope user \
  --env AZURE_DEVOPS_PAT=<your-pat> \
  --env AZURE_DEVOPS_PROJECT=<default-project> \
  -- npx -y azdo-mcp <your-organization>

On Windows, start the command with cmd /c: -- cmd /c npx -y azdo-mcp <your-organization>. In PowerShell, also write the separator as '--' (in quotes): claude runs through the claude.ps1 shim, and PowerShell drops a bare -- before calling a script, which makes claude fail with unknown option '-y'.

Claude Desktop — Settings → Developer → Edit Config and add to claude_desktop_config.json:

{
  "mcpServers": {
    "azure-devops": {
      "command": "npx",
      "args": ["-y", "azdo-mcp", "<your-organization>"],
      "env": {
        "AZURE_DEVOPS_PAT": "<your-pat>",
        "AZURE_DEVOPS_PROJECT": "<default-project>"
      }
    }
  }
}

Until the package is published on npm, use github:recepkucukekiz/azdo-mcp in place of azdo-mcp, or point to a local build: "command": "node", "args": ["C:/path/to/azdo-mcp/dist/index.js", "<your-organization>"].

Configuration

Read-only mode

With AZURE_DEVOPS_READ_ONLY=true (or the --read-only argument) the tools that create or change anything are not offered to the model at all. Use it together with a read-only PAT when you only want Claude to look things up.

Development

npm install
npm run build
npm test

npm run dev -- <org> runs the server from source (Node 22.18+ runs the TypeScript directly). The tests start the tools through a real MCP client against a fake Azure DevOps API, so they need no account.

To try the server interactively, use the MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js <your-organization>

Security notes

• The PAT gives the model whatever access the token has. Prefer short-lived tokens with only the scopes above, and read-only mode where you can.

• Text from work items, comments and files is shown to the model as data. Like any tool that reads content other people write, it can contain instructions aimed at the model; keep write tools behind your client's tool approval.

License

MIT