MCP Azure Devops

Azure DevOps boards, repos, pipelines & projects for AI agents — governed.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

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

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

mcp-azure-devops

A Model Context Protocol server for Azure DevOps. It lets an MCP-capable client (Claude Desktop, Claude Code, Cursor, Codex, …) work across boards, repos, pipelines, and projects — with a governance layer that keeps an AI agent inside safe boundaries.

What this offers

Projects & teams — list projects/teams/members, inspect process templates.
Boards / work items — WIQL queries, get work items, create/update work items, list iterations (sprints).
Repos / pull requests — list repositories and branches, list/get PRs, open PRs.
Pipelines / builds — list pipelines and recent builds, get a build, queue a run.
Admin / process — list process templates, create a project, delete a project (guarded).
Governance built in — access modes, project allowlists, protected projects, delete gating, typed confirmation for high-impact ops, dry-run, and JSON audit logging.

Governance & security model

Concern	Flag	Default	Effect
What can the server do?	`AZDO_MODE`	`read-only`	`read-only` → reads; `read-write` → work items, PRs, pipeline runs; `admin` → create/delete project. Tools above the mode are never registered.
Which projects are in scope?	`AZDO_PROJECT_ALLOWLIST`	(all)	Operations on other projects are refused.
Which projects are read-only forever?	`AZDO_PROTECTED_PROJECTS`	(none)	Readable, never mutable.
Can it delete?	`AZDO_ALLOW_DELETE`	`false`	`delete_project` needs this and admin mode.
Typed confirmation	`AZDO_REQUIRE_CONFIRMATION`	`true`	High-impact ops require `confirm` to equal the target name — not just a boolean.
Preview	`AZDO_DRY_RUN`	`false`	Write/admin tools validate + log intent, then return.
Audit trail	`AZDO_AUDIT_LOG`	`true`	JSON line to stderr per guarded operation.

Tools

Read (read-only+): list_projects, get_project, list_teams, list_team_members, list_processes, query_work_items, get_work_item, list_iterations, list_repositories, list_branches, list_pull_requests, get_pull_request, list_pipelines, list_builds, get_build

Write (read-write+): create_work_item, update_work_item, create_pull_request, run_pipeline

Admin (admin): create_project, delete_project (needs AZDO_ALLOW_DELETE + typed confirm)

Quickstart — add to your agent

Published on npm as @dockndevai/mcp-azure-devops. Runs via npx; needs an org and a PAT. See docs/CLIENTS.md for every client and .env.example for all variables.

Claude Code

Terminal

claude mcp add azure-devops -e AZDO_ORG_URL="https://dev.azure.com/your-org" -e AZDO_PAT="your-pat" -e AZDO_MODE="read-only" -- npx -y @dockndevai/mcp-azure-devops

Claude Desktop · Cursor · Windsurf

config.json

{
  "mcpServers": {
    "azure-devops": {
      "command": "npx",
      "args": ["-y", "@dockndevai/mcp-azure-devops"],
      "env": {
        "AZDO_ORG_URL": "https://dev.azure.com/your-org",
        "AZDO_PAT": "your-pat",
        "AZDO_MODE": "read-only"
      }
    }
  }
}

Example prompts

"List active pull requests in the Payments project's api repo"
"Query work items assigned to me that are still Active"
"Show the last 10 builds in the Web project and which failed"
"Create a Bug in Payments titled 'Checkout 500 on retry'" (needs read-write)

Run from source (development)

Terminal

npm install
npm run build
node dist/index.js   # with the environment variables set

Develop

Terminal

npm run dev
npm test          # governance policy: modes, allowlists, delete gating, confirmation
npm run typecheck

Publishing

Ships a server.json for the official MCP registry and an mcpName for npm ownership validation. See PUBLISHING.md.

License

MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Cloud Platforms View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about MCP Azure Devops

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "mcp-azure-devops": { "command": "npx", "args": ["-y", "mcp-azure-devops"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

MCP Azure Devops AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/mcp-azure-devops?style=directory)](https://allmcps.com/mcp/mcp-azure-devops)

HTML Embed

<a href="https://allmcps.com/mcp/mcp-azure-devops"><img src="https://allmcps.com/api/badge/mcp-azure-devops?style=directory" alt="MCP Azure Devops on AllMCPs" /></a>

Technical Specs & Signals

CategoryCloud Platforms

35Quality signal: Fair · 35/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools15/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in ☁️ Cloud Platforms →Best MCP servers for Cloud Platforms →Alternatives to MCP Azure Devops →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

mcp-azure-devops

What this offers

Projects & teams — list projects/teams/members, inspect process templates.
Boards / work items — WIQL queries, get work items, create/update work items, list iterations (sprints).
Repos / pull requests — list repositories and branches, list/get PRs, open PRs.
Pipelines / builds — list pipelines and recent builds, get a build, queue a run.
Admin / process — list process templates, create a project, delete a project (guarded).
Governance built in — access modes, project allowlists, protected projects, delete gating, typed confirmation for high-impact ops, dry-run, and JSON audit logging.

Governance & security model

Concern	Flag	Default	Effect
What can the server do?	`AZDO_MODE`	`read-only`	`read-only` → reads; `read-write` → work items, PRs, pipeline runs; `admin` → create/delete project. Tools above the mode are never registered.
Which projects are in scope?	`AZDO_PROJECT_ALLOWLIST`	(all)	Operations on other projects are refused.
Which projects are read-only forever?	`AZDO_PROTECTED_PROJECTS`	(none)	Readable, never mutable.
Can it delete?	`AZDO_ALLOW_DELETE`	`false`	`delete_project` needs this and admin mode.
Typed confirmation	`AZDO_REQUIRE_CONFIRMATION`	`true`	High-impact ops require `confirm` to equal the target name — not just a boolean.
Preview	`AZDO_DRY_RUN`	`false`	Write/admin tools validate + log intent, then return.
Audit trail	`AZDO_AUDIT_LOG`	`true`	JSON line to stderr per guarded operation.

Tools

Write (read-write+): create_work_item, update_work_item, create_pull_request, run_pipeline

Admin (admin): create_project, delete_project (needs AZDO_ALLOW_DELETE + typed confirm)

Quickstart — add to your agent

Published on npm as @dockndevai/mcp-azure-devops. Runs via npx; needs an org and a PAT. See docs/CLIENTS.md for every client and .env.example for all variables.

Claude Code

Terminal

claude mcp add azure-devops -e AZDO_ORG_URL="https://dev.azure.com/your-org" -e AZDO_PAT="your-pat" -e AZDO_MODE="read-only" -- npx -y @dockndevai/mcp-azure-devops

Claude Desktop · Cursor · Windsurf

config.json

{
  "mcpServers": {
    "azure-devops": {
      "command": "npx",
      "args": ["-y", "@dockndevai/mcp-azure-devops"],
      "env": {
        "AZDO_ORG_URL": "https://dev.azure.com/your-org",
        "AZDO_PAT": "your-pat",
        "AZDO_MODE": "read-only"
      }
    }
  }
}

Example prompts

"List active pull requests in the Payments project's api repo"
"Query work items assigned to me that are still Active"
"Show the last 10 builds in the Web project and which failed"
"Create a Bug in Payments titled 'Checkout 500 on retry'" (needs read-write)

Run from source (development)

Terminal

npm install
npm run build
node dist/index.js   # with the environment variables set

Develop

Terminal

npm run dev
npm test          # governance policy: modes, allowlists, delete gating, confirmation
npm run typecheck

Publishing

Ships a server.json for the official MCP registry and an mcpName for npm ownership validation. See PUBLISHING.md.

License

MIT