Skip to main content
Glama

mcp-azure-devops

CI License: MIT npm

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?

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 (delete_project, run_pipeline) prompt the human to approve via MCP elicitation before running. The prompt shows the tool, the exact arguments and a fingerprint; the target's version is pinned across the prompt and the action is refused if it changed; a prompt nobody answers is a refusal. delete_project also asks the human to type the project name (this is separate from the model-supplied confirm argument above, which is checked first and still required when AZDO_REQUIRE_CONFIRMATION=true).

Require a human

AZDO_REQUIRE_HUMAN_APPROVAL

false

When true, delete_project and run_pipeline are refused if the client cannot elicit (instead of falling back to the *_ALLOW_* gate alone).

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-devops

Claude 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 set

Develop

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

Available Tools

15 tools
get_buildGet buildA
Read-onlyIdempotent

Fetch a single build / pipeline run by id, with its status, result, and timing.

Inputs: buildId (required), project (required).

get_projectGet projectA
Read-onlyIdempotent

Fetch the full details (id, description, visibility, state, capabilities) of a single project.

Inputs: project (required).

get_pull_requestGet pull requestA
Read-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 itemA
Read-onlyIdempotent

Fetch a single work item by id, including all of its fields (title, state, assignee, tags, …).

Inputs: id (required).

list_branchesList branchesA
Read-onlyIdempotent

List the branches (refs/heads) of a Git repository, with the commit each one points at.

Inputs: repo (required), project (required).

list_buildsList buildsA
Read-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)A
Read-onlyIdempotent

List a team's iterations (sprints), each with its path and start/finish dates.

Inputs: team (required), project (required).

list_pipelinesList pipelinesA
Read-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 processesA
Read-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 projectsA
Read-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 requestsA
Read-onlyIdempotent

List pull requests in a repository, optionally filtered by status (active by default).

Inputs: repo (required), project (required), status.

list_repositoriesList repositoriesA
Read-onlyIdempotent

List the Git repositories in a project, with their ids, names, and default branches.

Inputs: project (required).

list_team_membersList team membersA
Read-onlyIdempotent

List the members (identities: display name and unique name) of a specific team within a project.

Inputs: team (required), project (required).

list_teamsList teamsA
Read-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)A
Read-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

    A4/5.0

    Scored across 15 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness2/5

    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

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers