Skip to content
Azure DevOps MCP Server

Azure DevOps MCP Server

by Microsoft
Released
v2.9.0
MIT
Repository Docs npm
Featured Developer Tools

Summary

Microsoft's official MCP server for Azure DevOps - work items, repos, pipelines, wikis, test plans and iterations, reachable from any MCP client in plain language.

Features

  • Read and manage work items, iterations and teams
  • Browse repositories, pull requests and builds
  • Query and trigger pipelines
  • Read, create and update wiki pages
  • List and inspect test plans
  • Hosted remote server over streamable HTTP, plus a local stdio option
  • Domain filtering and project/team defaults to limit tool surface

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Azure DevOps MCP Server" tools will be available.
{
  "mcpServers": {
    "azure-devops-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@azure-devops/mcp",
        "<your-ado-organization>"
      ]
    }
  }
}

Description

The Azure DevOps MCP Server brings your Azure DevOps organisation into an AI coding session. Rather than one giant do-everything tool, Microsoft built it as a set of small, focused tools that sit as a thin layer over the Azure DevOps REST API, leaving the reasoning to the model.

What you can ask it

Typical prompts the server is built for:

  • "List my ADO projects" or "List ADO repos for Contoso"
  • "List my work items for project Contoso" and "List work items in the current iteration for Contoso Team"
  • "List builds", "List test plans", "List teams", "List iterations"
  • "List all wikis in the Contoso project"
  • "Create a wiki page /Architecture/Overview with content about system design"
  • "Update the wiki page /Getting Started with new onboarding instructions"
Remote or local

Microsoft now recommends the remote server, hosted by Azure DevOps at https://mcp.dev.azure.com/{organization} over streamable HTTP - no install, and future development is focused there. The local stdio server published as @azure-devops/mcp on npm is still supported for scenarios that need it, and a nightly channel is available on the @next tag.

Setup notes

The local server needs Node.js 20+. Authentication happens through your Microsoft account: the first time a tool runs, a browser opens and asks you to sign in with credentials that match the Azure DevOps organisation you named. Beyond VS Code with GitHub Copilot, the project documents setup for Visual Studio 2022, Codex, Claude Code, Cursor, Opencode and Kilocode. Local configuration supports domain filtering and project/team defaults so an agent is not handed the whole organisation at once.

Microsoft also suggests adding a line to .github/copilot-instructions.md telling the agent that the project uses Azure DevOps, which noticeably improves tool selection.

MIT licensed, maintained in the open at microsoft/azure-devops-mcp.

Related MCP Servers

MCP: Buildkite MCP Server

by Buildkite

Buildkite's official MCP server: query pipelines, builds, jobs, logs, test runs and flaky-test data from an agent, over a hosted OAuth endpoint or a self-run binary.

Developer Tools

MCP: CircleCI MCP Server

by CircleCI

CircleCI's official MCP server: pull build failure logs, hunt flaky tests, validate config, trigger and rerun pipelines, and roll back - in natural language from your IDE.

Developer Tools
Browse all MCP servers →