Purpose: mcp-azure-devops is a Model Context Protocol server that lets MCP-capable clients (such as Claude Desktop, Claude Code, Cursor, Codex) perform operations across Azure DevOps boards, repositories, pipelines, and projects, and constrains AI agents within safe boundaries through a governance layer.
Main capabilities: Projects and teams—list projects/teams/members, view process templates; Boards/work items—WIQL queries, get work items, create/update work items, list iterations (sprints); Repositories/pull requests—list repositories and branches, list/get PRs, create PRs; Pipelines/builds—list pipelines and recent builds, get builds, queue runs; Administration/process—list process templates, create projects, delete projects (protected).
Governance and security model: tiered by operation. 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 (requires AZDO_ALLOW_DELETE plus input-based confirmation). In addition, there are project allowlists, protected projects, delete gating, dry-run, and JSON audit logs.
Usage: This server is published on npm under the package name @dockndevai/mcp-azure-devops, runs via npx, and requires an organization and PAT. See docs/CLIENTS.md for client configurations and .env.example for all environment variables. It can be run fromsource (development), provides server.json for the official MCP registry, and provides mcpName for npm ownership verification.
Use cases: Let AI clients query or update Azure DevOps work items, view project repositories and pull requests, check build and pipeline status, and impose governance constraints on read, write, and admin operations.
Limitations: Specific pricing, performance metrics, and complete installation command information are not yet provided; high-impact operations are restricted by access mode, project scope, protected projects, and delete confirmation; an Azure DevOps organization and PAT are required before use.
