microsoft/azure-devops-mcp

> [!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.
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