Warning
We recently completed a full tool consolidation that includes renaming of existing tools. Please see the
If this is a breaking change for your agents or skills, you can temporarily pin the version to @azure-devops/mcp@2.8.1
This project provides Azure DevOps MCP tooling for AI agents, with a remote-first onboarding experience and a local server option when you need it.
Important
We recommend using the Remote MCP Server instead of this local server. It requires no installation and gets new features first.
- 📺 Overview
- 🏆 Expectations
- 🚀 Remote MCP Server (Recommended)
- ⚙️ Supported Tools
- 🔌 Local MCP Server Installation (Optional)
- 🌏 Using Domains (local)
- 🐥 Project and Team Defaults (local)
- 📝 Troubleshooting
- 🎩 Examples & Best Practices
- 🙋♀️ Frequently Asked Questions
- 📌 Contributing
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"
The Azure DevOps MCP Server is built around tools that are concise, simple, focused, and easy to use, with each one designed for a specific scenario. We intentionally avoid creating complex tools that try to do too much. The goal is to provide a thin abstraction layer over the REST APIs that makes data access straightforward while allowing the language model to handle the more complex reasoning.