mcp-azure-devops
An MCP server for Azure DevOps that lets an AI client browse boards, repos, pipelines, and projects under a built-in governance layer.
Projects & teams: list projects (allowlist-filtered, flagged if protected), get project details, list teams and team members, list process templates.
Work items: run WIQL queries, fetch a work item's full fields, list a team's iterations/sprints.
Repos & PRs: list repositories and branches, list pull requests by status, get a PR's branches/status/reviewers.
Pipelines & builds: list pipelines, list recent builds, get a build's status and timing.
Writes (read-write mode): create/update work items, create pull requests, queue pipeline runs.
Admin (admin mode): create projects, delete projects (needs
AZDO_ALLOW_DELETEplus typed confirmation).Governance: mode gating (
read-only/read-write/admin), project allowlists, protected projects, dry-run, audit logging, and human elicitation for destructive actions.
Note: the supplied schema registers only the read-only tool set.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-azure-devops List active pull requests in the Payments project's api repo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: Azure DevOps MCP Server
Governance & security model
Concern | Flag | Default | Effect |
What can the server do? |
|
|
|
Which projects are in scope? |
| (all) | Operations on other projects are refused. |
Which projects are read-only forever? |
| (none) | Readable, never mutable. |
Can it delete? |
|
|
|
Typed confirmation |
|
| High-impact ops require |
Preview |
|
| Write/admin tools validate + log intent, then return. |
Audit trail |
|
| JSON line to stderr per guarded operation. |
Interactive confirmation | (automatic) | — | Destructive & high-impact actions ( |
Require a human |
|
| When |
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
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-devopsClaude Desktop · Cursor · Windsurf
{
"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)
npm install
npm run build
node dist/index.js # with the environment variables setDevelop
npm run dev
npm test # governance policy: modes, allowlists, delete gating, confirmation
npm run typecheckPublishing
Ships a server.json for the official MCP registry and an mcpName for npm ownership validation. See PUBLISHING.md.
License
MIT
Available Tools
15 toolsget_buildGet buildARead-onlyIdempotent
Fetch a single build / pipeline run by id, with its status, result, and timing.
Inputs: buildId (required), project (required).
get_projectGet projectARead-onlyIdempotent
Fetch the full details (id, description, visibility, state, capabilities) of a single project.
Inputs: project (required).
get_pull_requestGet pull requestARead-onlyIdempotent
Fetch a single pull request by id, including its source/target branches, status, and reviewers.
Inputs: id (required), repo (required), project (required).
get_work_itemGet work itemARead-onlyIdempotent
Fetch a single work item by id, including all of its fields (title, state, assignee, tags, …).
Inputs: id (required).
list_branchesList branchesARead-onlyIdempotent
List the branches (refs/heads) of a Git repository, with the commit each one points at.
Inputs: repo (required), project (required).
list_buildsList buildsARead-onlyIdempotent
List recent builds / pipeline runs in a project, most recent first, with their status and result.
Inputs: project (required), top.
list_iterationsList iterations (sprints)ARead-onlyIdempotent
List a team's iterations (sprints), each with its path and start/finish dates.
Inputs: team (required), project (required).
list_pipelinesList pipelinesARead-onlyIdempotent
List the pipelines defined in a project, with their ids and names. Use a pipeline id with run_pipeline.
Inputs: project (required).
list_processesList processesARead-onlyIdempotent
List the organization's process templates (Agile, Scrum, CMMI, or inherited) with their ids. Pass one of these ids as the process when creating a project.
Inputs: no named parameters.
list_projectsList projectsARead-onlyIdempotent
List the projects in the Azure DevOps organization that pass the allowlist. Returns each project's id, name, state, and whether it is marked protected (readable but never mutated). Start here to discover valid project names.
Inputs: no named parameters.
list_pull_requestsList pull requestsARead-onlyIdempotent
List pull requests in a repository, optionally filtered by status (active by default).
Inputs: repo (required), project (required), status.
list_repositoriesList repositoriesARead-onlyIdempotent
List the Git repositories in a project, with their ids, names, and default branches.
Inputs: project (required).
list_team_membersList team membersARead-onlyIdempotent
List the members (identities: display name and unique name) of a specific team within a project.
Inputs: team (required), project (required).
list_teamsList teamsARead-onlyIdempotent
List the teams defined in a project, with their ids and names. Use a team id/name with the team-scoped tools.
Inputs: project (required).
query_work_itemsQuery work items (WIQL)ARead-onlyIdempotent
Run a Work Item Query Language (WIQL) query against a project and return the matching work-item ids (fetch fields with get_work_item). Example: SELECT [System.Id] FROM WorkItems WHERE [System.State] = 'Active'.
Inputs: wiql (required), project (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 15 tools
Each tool targets a distinct Azure DevOps resource or action: projects, teams, team members, processes, work items, iterations, repositories, branches, pull requests, pipelines, and builds. list_* and get_* pairs are clearly complementary rather than overlapping, and query_work_items vs get_work_item is a clear search-then-fetch workflow.
Tool names follow a consistent list_<resource> and get_<resource> snake_case convention, with query_work_items as the only special-case verb. No mixed casing or vague verbs like 'process' or 'run' appear, making the naming predictable and easy to navigate.
Fifteen tools is at the upper edge of the well-scoped range but still appropriate: each tool covers a meaningful read operation on a distinct Azure DevOps entity, and none feel redundant. The count reflects a focused read-only browsing surface rather than an unwieldy grab bag.
The set covers read-only browsing across major Azure DevOps entities, but it has no create, update, delete, or run operations at all. This is especially problematic because list_processes references creating a project and list_pipelines references run_pipeline, yet neither create_project nor run_pipeline is exposed, leaving agents with dead ends and incomplete workflows.
Maintenance
Related MCP Connectors
Operate GitHub from your AI assistant: repos, PRs, issues, Actions. Previews and read-only mode.
Fail-closed policy guardrails for AI agents running kubectl, terraform, helm, and argocd.
Plan Salesforce deploys, open pull requests and trigger pipelines from your AI client.
Runtime permission, approval, and audit layer for AI agent tool execution.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps to manage work items, Git repositories, branches, commits, and projects through natural language commands.1,134 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Azure DevOps APIs for managing projects, work items, repositories, pull requests, and pipelines through natural language.29 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps entities like projects, repositories, work items, pull requests, and pipelines.15 npm17MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps APIs for managing projects, work items, repositories, pull requests, pipelines, and more through natural language.5,492 npmMIT