MCP (Model Context Protocol) servers provide tools that agents call to interact with external systems. They extend agent capabilities beyond file and code operations.
GitHub
Transport: HTTP (https://api.githubcopilot.com/mcp/)
Toolsets: repos, issues, pull_requests, projects, labels, users, copilot, actions, code_security, secret_protection, security_advisories, dependabot.
Used by: Most agents (envision, kickoff, specify, decompose, implement, sprint, refine, review, security)
Azure DevOps
Transport: HTTP (https://mcp.dev.azure.com/)
Remote MCP server (public preview). Authenticates via Microsoft Entra ID (OAuth). No local installation required.
Toolsets enabled via X-MCP-Toolsets header:
| Toolset | Purpose |
|---|---|
wit | Work item CRUD, hierarchy management, traceability links, board management |
work | Sprint planning, team iterations, team capacity |
search | Duplicate detection, backlog queries |
repos | PR creation, review threads, branch management for ADO-hosted repos |
Used by: envision, kickoff, specify, decompose, implement, sprint, refine
Azure
Transport: stdio (npx @azure/mcp@latest server start)
Architecture guidance, deployment operations, pricing estimation, best practices, compliance checking.
Used by: plan, decompose, implement, security
Microsoft Learn
Transport: HTTP (https://learn.microsoft.com/api/mcp)
Official Microsoft documentation lookup, API references, code samples, security guidance.
Used by: plan, implement, review, security
Draw.io
Transport: HTTP (https://mcp.draw.io/mcp)
Create and edit architecture diagrams, threat models, system diagrams.
Used by: plan, security
MCP servers are configured in .mcp.json at the plugin root. The VS Code workspace-level .vscode/mcp.json can override or extend the configuration.
