Azure DevOps (ADO)

io.github.PremierIncPublished by GitHub account PremierIncvv0.0.1Updated Oct 28, 2026

The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Hosted Azure DevOps MCP server that lets an assistant read and update projects, repos, pipelines, work items, test plans and wikis in an organization.

What you can do
  • List projects, teams and iterations in an Azure DevOps organization
  • List repositories and builds for a project
  • List and query work items, including those in the current iteration
  • List test plans
  • List wikis and read, create or update wiki pages
When to use it
Useful when an assistant should answer questions or make changes inside Azure DevOps without leaving the chat, for example summarizing work items, checking builds or editing wiki documentation. The hosted remote server is the recommended setup for most clients.
Requirements
A remote endpoint at mcp.dev.azure.com with the organization name in the URL, plus OAuth sign-in with a Microsoft account that has access to that Azure DevOps organization. The Authorization header carries a PAT or app token when used that way. A local stdio variant exists via an npm package and needs Node.js 20 or later.
Before you install
Access is tied to your Azure DevOps organization and the signed-in account's permissions. Some tools create or update content, such as wiki pages, so changes can be written to shared project data. The Authorization header carries a secret token; keep it out of shared configuration files.

Installation

In SourceWeft

  1. Open Azure DevOps (ADO) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.PremierInc%2Fazure-devops/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "azure-devops-ado": {
      "type": "http",
      "url": "https://mcp.dev.azure.com/"
    }
  }
}

README

Azure DevOps MCP Server

[!IMPORTANT] We recommend using the Remote MCP Server instead of this local server. It requires no installation and gets new features first.

Learn more

This project gives AI agents access to Azure DevOps through the Model Context Protocol (MCP). Use the hosted remote server for the simplest setup, or run the local server when you need a stdio connection.

Table of Contents

  1. Overview
  2. Design
  3. Remote MCP Server (Recommended)
  4. Supported Tools
  5. Local MCP Server Installation (Optional)
  6. Using Domains (Local Server)
  7. Project and Team Defaults (Local Server)
  8. Troubleshooting
  9. Examples and Best Practices
  10. Frequently Asked Questions
  11. Contributing

Overview

The Azure DevOps MCP Server brings Azure DevOps context to your agents. Try prompts like:

  • "List my ADO projects"
  • "List ADO Builds for 'Contoso'"
  • "List ADO Repos for 'Contoso'"
  • "List test plans for 'Contoso'"
  • "List teams for project 'Contoso'"
  • "List iterations for project 'Contoso'"
  • "List my work items for project 'Contoso'"
  • "List work items in current iteration for 'Contoso' project and 'Contoso Team'"
  • "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"
  • "Get the content of the wiki page '/API/Authentication' from the Documentation wiki"

Design

Each tool handles a focused Azure DevOps task. The server provides a thin layer over the REST APIs, while the AI agent handles higher-level reasoning.

Remote MCP Server (Recommended)

For complete instructions, see the Remote MCP Server onboarding documentation.

The remote server will eventually replace the local server. The local server remains supported, but new development will focus on the remote server. Existing local server users should begin planning their migration.

If you encounter issues with tools, need support, or have a feature request, you can report an issue using the Remote MCP Server issue template. During the preview period, we will track Remote MCP Server issues through this repository.

Quick Start

Create .vscode/mcp.json in your project and add this configuration. Replace {organization} with your Azure DevOps organization name.

json
{  "servers": {    "ado-remote-mcp": {      "url": "https://mcp.dev.azure.com/{organization}",      "type": "http"    }  },  "inputs": []}

See the remote server configuration documentation for more options.

After saving .vscode/mcp.json, start the server from the MCP view in VS Code, then run a prompt like List ADO projects.

Supported Tools

See the Available Tools documentation for the complete list of available remote tools.

For the complete list of local tools, see TOOLSET.md.

Local MCP Server Installation (Optional)

[!IMPORTANT] Start with the Remote MCP Server first. Use the local MCP Server only if your scenario specifically requires a local stdio setup.

These steps use Visual Studio Code and GitHub Copilot. For other supported clients, including Visual Studio 2022, Codex, Claude Code, Cursor, OpenCode, and Kilo Code, see the getting started guide.

Prerequisites

  1. Install VS Code or VS Code Insiders.
  2. Install Node.js 20 or later.
  3. Open your project in VS Code.

Installation

Install from npm
  1. Create .vscode/mcp.json in your project.
  2. Add this configuration:
json
{  "servers": {    "ado": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@azure-devops/mcp", "{organization}"]    }  }}
  1. Save the file, then start the ado server from the MCP view in VS Code.
  2. Open GitHub Copilot Chat and switch to Agent mode.
  3. Select the Azure DevOps tools, then try a prompt such as List ADO projects.
  4. When prompted, sign in with a Microsoft account that has access to the selected Azure DevOps organization.

To use nightly builds, replace @azure-devops/mcp with @azure-devops/mcp@next in the configuration.

For better tool selection, add .github/copilot-instructions.md to your project with this instruction:

text
This project uses Azure DevOps. Always check whether the Azure DevOps MCP server has a tool relevant to the user's request.

Using Domains (Local Server)

The local server includes many tools. Domains let you load only the tool groups you need, which keeps the tool list manageable and helps clients with tool limits. Available domains are core, work, work-items, search, test-plans, repositories, wiki, pipelines, and advanced-security.

Add -d followed by the domains to the server arguments. For example, this configuration loads only work item-related tools:

json
{  "servers": {    "ado_with_filtered_domains": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@azure-devops/mcp", "{organization}", "-d", "core", "work", "work-items"]    }  }}

Always include core so the agent can retrieve project information.

If you omit -d, the server loads all domains.

Project and Team Defaults (Local Server)

Set default Azure DevOps project and team values in .vscode/mcp.json so tools can skip selection prompts.

Example .vscode/mcp.json

json
{  "servers": {    "ado": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@azure-devops/mcp", "{organization}", "--authentication", "azcli"],      "env": {        "ado_mcp_project": "Contoso",        "ado_mcp_team": "Fabrikam Team"      }    }  }}

Troubleshooting

See the Troubleshooting guide for help with common issues and logging.

Examples

See the examples for sample prompts.

Frequently Asked Questions

For answers to common questions about the Azure DevOps MCP Server, see the Frequently Asked Questions.

Contributing

We welcome contributions. During preview, file issues for bugs, enhancements, or documentation improvements.

See our Contributions Guide for:

  • Development setup
  • Adding new tools
  • Code style and testing
  • Pull request process

Read the Contributions Guide before creating a pull request.

Code of Conduct

This project follows the Microsoft Open Source Code of Conduct. For questions, see the FAQ or contact [email protected].

Hall of Fame

Thanks to all contributors who make this project awesome! ❤️

[Contributors]

Generated with contrib.rocks

License

Licensed under the MIT License.

Trademarks: This project may include trademarks or logos for Microsoft or third parties. Use of Microsoft trademarks or logos must follow Microsoft’s Trademark & Brand Guidelines. Third-party trademarks are subject to their respective policies.

Source: README.md at commit 3ee829c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. vv0.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts