Power your agent
URL ของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
https://mcp.dev.azure.comปุ่ม Claude ด้านบนจะเปิด Claude พร้อมกรอกชื่อและ URL ให้แล้ว คุณยังต้องยืนยันที่นั่นเอง
claude mcp add --transport http io.github.premierinc-azure-devops https://mcp.dev.azure.comRun in a terminal.
{ "mcpServers": { "io.github.premierinc-azure-devops": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.dev.azure.com" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
[!IMPORTANT] 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 connection.
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
stdioThe Azure DevOps MCP Server brings Azure DevOps context to your agents. Try prompts like:
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.
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.
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.
See the Available Tools documentation for the complete list of available remote tools.
For the complete list of local tools, see TOOLSET.md.
[!IMPORTANT] Start with the Remote MCP Server first. Use the local MCP Server only if your scenario specifically requires a local
stdiosetup.
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.
.vscode/mcp.json in your project.{
"servers": {
"ado": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@azure-devops/mcp", "{organization}"]
}
}
}
ado server from the MCP view in VS Code.List ADO projects.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.
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.
Set default Azure DevOps project and team values in .vscode/mcp.json so tools can skip selection prompts.
.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"
}
}
}
}
See the Troubleshooting guide for help with common issues and logging.
See the examples for sample prompts.
For answers to common questions about the Azure DevOps MCP Server, see the Frequently Asked Questions.
We welcome contributions. During preview, file issues for bugs, enhancements, or documentation improvements.
See our Contributions Guide for:
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].
Thanks to all contributors who make this project awesome! ❤️
Generated with contrib.rocks
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.
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
{ "mcpServers": { "io.github.premierinc-azure-devops": { "url": "https://mcp.dev.azure.com", "headers": {} } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก http สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Azure DevOps (ADO) เข้าถึงได้ผ่าน HTTP
ตรวจสอบล่าสุดเมื่อ 2026-11-09 The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.