Azure DevOps MCP Server
Важно
We recommend using the Remote MCP Server instead of this local server. It requires no installation and gets new features first.
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
- Overview
- Design
- Remote MCP Server (Recommended)
- Supported Tools
- Local MCP Server Installation (Optional)
- Using Domains (Local Server)
- Project and Team Defaults (Local Server)
- Troubleshooting
- Examples and Best Practices
- Frequently Asked Questions
- 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"






