Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Azure DevOps (ADO)

by microsoftversion v0.0.1i★ –iRuns in the cloud
Registry nameio.github.PremierInc/azure-devops

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Developer tools
  • You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 0 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http azure-devops https://mcp.dev.azure.com --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "azure-devops": {
      "url": "https://mcp.dev.azure.com",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "azure-devops": {
      "type": "http",
      "url": "https://mcp.dev.azure.com",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization secret HTTP header
    Authorization header with authentication token (PAT or App token)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ! Caution

    Maker matches the repo

    The publisher (PremierInc) is not the repo owner (microsoft); someone else may have listed it

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

  • More stars than 0% of the other 1387 servers in this category
  • Published to the registry more recently than 22% of the other 1387 servers in this category
  • Basic checks equal to or better than 23% of the other 1387 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Azure DevOps (ADO) safe?

It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (v0.0.1) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

{

"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:
{

"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:

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:

{

"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
{

"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 open@microsoft.com.

Hall of Fame

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

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._

Ask PopNx