VS Code has native MCP support (no extension needed) as of version 1.93. Configure servers at `.vscode/mcp.json` per project with a `servers` key (note: different from Claude Code's `mcpServers`). GitHub Copilot's agent mode invokes them automatically. Best choice if your team already runs VS Code + Copilot Enterprise.
Microsoft's flagship editor with Copilot Chat agent mode and native MCP support
.vscode/mcp.json (per project) or settings.json (global){
"servers": {
"github": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${input:github_pat}"
}
},
"supabase": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@supabase/mcp-server-supabase@latest"],
"env": {
"SUPABASE_URL": "https://your-project.supabase.co",
"SUPABASE_SERVICE_ROLE_KEY": "${input:sb_key}"
}
}
},
"inputs": [
{ "id": "github_pat", "type": "promptString", "description": "GitHub PAT", "password": true },
{ "id": "sb_key", "type": "promptString", "description": "Supabase service role key", "password": true }
]
}Real secrets should never be committed — use environment variables or your editor's secrets manager.
Obvious pairing — Microsoft owns both VS Code and GitHub. Copilot + GitHub MCP is the smoothest combo in the ecosystem.
Most popular data MCP among Copilot users. Works flawlessly with the VS Code MCP stdio transport.
DB introspection and query execution inside the editor. Copilot's inline chat makes DB exploration natural.
Billing-aware coding — Copilot reads Stripe state while implementing subscription logic.
Turn Copilot agent-mode tasks into Linear tickets and close them when the PR merges.
Pull specs into Copilot's context without copy-paste. Essential for spec-driven dev teams.
Fetch error context into the chat. Copilot then proposes fixes based on the actual trace.
Manage containers from the VS Code terminal via Copilot agent mode — inspect, restart, exec.
Debug deploys without leaving the editor. Build logs and preview URLs surface in Copilot chat.
Microsoft owns Playwright too — first-class integration. Copilot writes and runs E2E tests as a single flow.
GitHub MCP — Microsoft owns both, so the integration is seamless. After that: Supabase/Postgres for data, Linear for tickets, Sentry for debugging, Playwright for tests (also Microsoft-owned).
The MCP protocol is free and built into VS Code. But you need Copilot (Free/Pro/Business/Enterprise) to use agent mode, which is where MCPs become useful. Free tier works but has request limits.
Per project: `.vscode/mcp.json`. User-level: in `settings.json` under `mcp.servers`. The schema uses `servers` (not `mcpServers` like Claude Code) and supports `inputs` for prompted secrets.
Mostly yes — the inner `command/args/env` shape is identical. Only the outer key differs (`mcpServers` vs `servers`). A quick rename transforms one into the other.
Yes — that's the main value prop. Ask Copilot 'add a Stripe webhook handler for failed payments' and it'll call the Stripe MCP to check your setup, the GitHub MCP to open a PR, and Linear MCP to log the ticket. One prompt, multiple MCPs.
Pick from the top 10 curated above, or browse the full marketplace of 100+ MCPs.