claude mcp add mcp-azure-devops -- npx -y mcp-azure-devops
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
1 ★ · dockndevai/mcp-azure-devops · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 1 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository dockndevai/mcp-azure-devops;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
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. | | Interactive confirmation | *(automatic)* | — | Destructive & high-impact actions prompt the human to approve via MCP elicitation before running; clients without elicitation fall back to the *_ALLOW_* gate. | 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)