Skip to content
This project is under active development and subject to breaking changes. See the changelog for release notes.

MCP Servers

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: stdio (npx @azure-devops/mcp@next)

Work item CRUD, hierarchy management (parent-child), traceability links, board management. Requires organization name input.

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.