Log inSubmit server
A

Azure DevOps (ADO)

Connects AI agents to Azure DevOps projects, work items, repositories, pipelines, tests, wikis, and more through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Azure DevOps (ADO)

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "azure-devops-ado": {
      "command": "npx",
      "args": [
        "-y",
        "@azure-devops/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Azure DevOps (ADO) MCP server connects AI agents to Azure DevOps through focused MCP tools backed by Azure DevOps REST APIs. It supports a hosted remote endpoint for simpler setup and a local Node.js package when a stdio connection is required. Use it to query projects, teams, work items, repositories, builds, test plans, iterations, and wikis, or to create and update wiki pages. The local server can load selected tool domains and apply project or team defaults.

Use cases

  • List projects, teams, iterations, and work items
  • Search repositories and inspect build information
  • Retrieve test plans and current-iteration work items
  • Create or update Azure DevOps wiki pages
  • Filter local tools by Azure DevOps domain

Key features

  • Remote HTTP MCP endpoint
  • Local stdio server via npm
  • Project, work item, repository, and pipeline tools
  • Test plan and wiki operations
  • Selectable local tool domains
  • Project and team defaults

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

40/42 checks healthy over the last 91d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @azure-devops/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2.1kStargazers on the source repository.
npm downloads581kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Directory activity11 viewsConfig copies, upvotes, and views on AllMCPs.

How Azure DevOps (ADO) works

What Azure DevOps (ADO) MCP server does

Azure DevOps (ADO) MCP server exposes Azure DevOps operations to AI agents through the Model Context Protocol. Its tools cover common development and project-management data, including projects, teams, iterations, work items, repositories, builds, test plans, and wikis. Wiki tools can retrieve page content and create or update pages.

The server uses focused tools for individual Azure DevOps tasks. It provides a relatively thin MCP layer over Azure DevOps REST APIs, leaving the agent to interpret requests and combine results into a response or workflow.

How it works

Two connection options are available. The recommended option is Microsoft’s hosted remote MCP server, reached at an organization-specific HTTP URL such as https://mcp.dev.azure.com/{organization}. This option avoids installing the local package and is intended to receive new features first.

The alternative is a local server launched through npx with the @azure-devops/mcp package. It communicates over stdio and takes the Azure DevOps organization as an argument. After connecting, the agent can select the relevant Azure DevOps tools and authenticate with a Microsoft account that can access the organization.

Setup and configuration

For the remote server, add an HTTP server entry to .vscode/mcp.json, replacing {organization} with the Azure DevOps organization name. Start the server from VS Code’s MCP view, then send a request such as listing the organization’s projects.

The local setup requires VS Code or VS Code Insiders, Node.js 20 or newer, and a project opened in VS Code. A typical configuration runs npx -y @azure-devops/mcp {organization} with the stdio transport. The package also has a next tag for nightly builds.

Local configurations may set ado_mcp_project and ado_mcp_team environment values to provide default project and team selections. Authentication can be configured with the azcli option in the server arguments.

Tools and capabilities

Local tools can be grouped into domains so clients receive a smaller tool set. Available domains are:

  • core
  • work
  • work-items
  • search
  • test-plans
  • repositories
  • wiki
  • pipelines
  • advanced-security

Include core when using domain filtering so the agent can obtain project information. Without a domain filter, the local server loads all domains.

Limitations and notes

Microsoft recommends the remote server for new deployments and expects it to replace the local server over time. The local option remains supported for scenarios that specifically require stdio, but development is focused on the hosted service.

The server does not replace the agent’s reasoning layer: individual tools handle Azure DevOps tasks while the agent determines which operations to call. Access also depends on signing in with an account that has permission to use the selected Azure DevOps organization.

Read the full README View source on GitHub

Reviews

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

Frequently Asked Questions about Azure DevOps (ADO)

Azure DevOps (ADO) is an MCP server that connects AI agents to Azure DevOps organizations through remote HTTP or local stdio connections. Its main tools cover projects, teams, work items, repositories, builds, pipelines, test plans, iterations, and wikis, including wiki page creation, updates, and content retrieval.

Use the hosted remote server when possible, or run the local package with Node.js 20 or newer. For local use, add an `npx -y @azure-devops/mcp {organization}` stdio entry to `.vscode/mcp.json`, start it from VS Code’s MCP view, and sign in with an authorized Microsoft account.

Yes, Azure DevOps (ADO) supports Cursor through its local MCP setup. Configure the server using the getting-started instructions for supported clients, provide the Azure DevOps organization, and authenticate with an account that can access that organization.

Yes, the local server supports domain filtering with the `-d` argument. Choose domains such as `work-items`, `repositories`, `wiki`, or `pipelines` to keep the available tool list smaller, and include the `core` domain so project information can be retrieved.

Add an HTTP MCP entry using `https://mcp.dev.azure.com/{organization}` to `.vscode/mcp.json`, replacing the placeholder with your organization name. Start it from the VS Code MCP view, then authenticate and send an Azure DevOps request such as listing projects.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

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 PreviewAzure DevOps (ADO) AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/azure-devops-ado?style=directory)](https://allmcps.com/mcp/azure-devops-ado)
HTML Embed
<a href="https://allmcps.com/mcp/azure-devops-ado"><img src="https://allmcps.com/api/badge/azure-devops-ado?style=directory" alt="Azure DevOps (ADO) on AllMCPs" /></a>