by microsoft
Boost your productivity by managing Azure DevOps projects, pipelines, and repos in VS Code. Streamline dev workflows wit
★ 1.4K
GitHub stars
Brings Azure DevOps functionality directly into VS Code, letting you manage projects, pull requests, work items, and repositories from your editor. Streamlines DevOps workflows without switching between tools.
Azure DevOps is an official MCP server published by microsoft that provides AI assistants with tools and capabilities via the Model Context Protocol. Boost your productivity by managing Azure DevOps projects, pipelines, and repos in VS Code. Streamline dev workflows wit It is categorized under developer tools, productivity. This server exposes 77 tools that AI clients can invoke during conversations and coding sessions.
You can install Azure DevOps in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Azure DevOps is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: Azure DevOps is the kind of server we cite when onboarding engineers to host + tool permissions.
Azure DevOps reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Azure DevOps reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Azure DevOps for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
I recommend Azure DevOps for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Azure DevOps surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend Azure DevOps for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Azure DevOps surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Strong directory entry: Azure DevOps surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, Azure DevOps benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 35
Easily install the Azure DevOps MCP Server for VS Code or VS Code Insiders:
This TypeScript project provides a local MCP server for Azure DevOps, enabling you to perform a wide range of Azure DevOps tasks directly from your code editor.
The Azure DevOps MCP Server brings Azure DevOps context to your agents. Try prompts like:
The Azure DevOps MCP Server is built from tools that are concise, simple, focused, and easy to use—each designed for a specific scenario. We intentionally avoid complex tools that try to do too much. The goal is to provide a thin abstraction layer over the REST APIs, making data access straightforward and letting the language model handle complex reasoning.
See TOOLSET.md for a comprehensive list.
For the best experience, use Visual Studio Code and GitHub Copilot. See the getting started documentation to use our MCP Server with other tools such as Visual Studio 2022, Claude Code, and Cursor.
After installation, select GitHub Copilot Agent Mode and refresh the tools list. Learn more about Agent Mode in the VS Code Documentation.
This installation method is the easiest for all users of Visual Studio Code.
🎥 Watch this quick start video to get up and running in under two minutes!
In your project, add a .vscode\mcp.json file with the following content:
{
"inputs": [
{
"id": "ado_org",
"type": "promptString",
"description": "Azure DevOps organization name (e.g. 'contoso')"
}
],
"servers": {
"ado": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@azure-devops/mcp", "${input:ado_org}"]
}
}
}
🔥 To stay up to date with the latest features, you can use our nightly builds. Simply update your mcp.json configuration to use @azure-devops/mcp@next. Here is an updated example:
{
"inputs": [
{
"id": "ado_org",
"type": "promptString",
"description": "Azure DevOps organization name (e.g. 'contoso')"
}
],
"servers": {
"ado": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@azure-devops/mcp@next", "${input:ado_org}"]
}
}
}
Save the file, then click 'Start'.
In chat, switch to Agent Mode.
Click "Select Tools" and choose the available tools.
Open GitHub Copilot Chat and try a prompt like List ADO projects. The first time an ADO tool is executed browser will open prompting to login with your Microsoft account. Please ensure you are using credentials matching selected Azure DevOps organization.
💥 We strongly recommend creating a
.github\copilot-instructions.mdin your project. This will enhance your experience using the Azure DevOps MCP Server with GitHub Copilot Chat. To start, just include "This project uses Azure DevOps. Always check to see if the Azure DevOps MCP server has a tool relevant to the user's request" in your copilot instructions file.
See the getting started documentation to use our MCP Server with other tools such as Visual Studio 2022, Claude Code, and Cursor.
Azure DevOps exposes a large surface area. As a result, our Azure DevOps MCP Server includes many tools. To keep the toolset manageable, avoid confusing the model, and respect client limits on loaded tools, use Domains to load only the areas you need. Domains are named groups of related tools (for example: core, work, work-items, repositories, wiki). Add the -d argument and the domain names to the server args in your mcp.json to list the domains to enable.
For example, use "-d", "core", "work", "work-items" to load only Work Item related tools (see the example below).
{
"inputs": [
{
"id": "ado_org",
"type": "promptString",
"description": "Azure DevOps organization name (e.g. 'contoso')"
}
],
"servers": {
"ado_with_filtered_domains": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@azure-devops/mcp", "${input:ado_org}", "-d", "core", "work", "work-items"]
}
}
}
Domains that are available are: core, work, work-items, search, test-plans, repositories, wiki, pipelines, advanced-security
We recommend that you always enable core tools so that you can fetch project level information.
By default all domains are loaded
See the Troubleshooting guide for help with common issues and logging.
Explore example prompts in our Examples documentation.
For best practices and tips to enhance your experience with the MCP Server, refer to the How-To guide.
For answers to common questions about the Azure DevOps MCP Server, see the Frequently Asked Questions.
We welcome contributions! During preview, please file issues for bugs, enhancements, or documentation improvements.
See our Contributions Guide for:
⚠️ Please read the Contributions Guide before creating a pull request.
This project follows the Microsoft Open Source Code of Conduct. For questions, see the FAQ or contact [email protected].
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.