How to add an MCP server to VS Code (Copilot Chat) — 2026 guide

How Plugsky MCP works in practice

Everything in this guide runs on Plugsky’s live MCP endpoint (https://plugsky.com/mcp) or the npm bridge (npx -y @plugsky/mcp). A client request flows: JSON-RPC over Streamable-HTTP → auth (API key or OAuth 2.1 + Dynamic Client Registration with fine-grained scopes) → tool router → the service you asked for. Model calls run behind a 7-tier provider failover chain; browsing renders with headless Chromium; transcripts come from real captions and Groq Whisper; images generate on FLUX; code runs in a sandbox with no network; memory persists in your account (Postgres-backed); and every tool call is metered per user on your dashboard.

Relevant live tools for this article: all 20 tools over stdio via the VS Code servers config.

How to add an MCP server to VS Code (Copilot Chat) — 2026 guide

Direct answer

To add an MCP server to VS Code Copilot Chat in 2026: create .vscode/mcp.json in your project (or use the global user settings). The top-level key is servers — NOT mcpServers (a common mistake copied from Claude configs). Add each server with a command (stdio) or url (Streamable-HTTP). Save; VS Code detects the file and offers a "Start" action. Once running, tools appear in the Copilot Chat tool picker.

Key facts

Project config	.vscode/mcp.json
Top-level key	servers ⚠️ (not mcpServers)
Global config	User settings.json → mcp.servers
Transports	stdio, Streamable-HTTP
Auth	OAuth 2.1, Bearer, stdio env
Primitives	Tools (full), Resources (partial)
Reload	Prompted on file change
Interface	Copilot Chat panel
Requires	GitHub Copilot subscription (Business or higher recommended for MCP)
Directory	GitHub Marketplace has featured MCPs

TL;DR

• VS Code uses .vscode/mcp.json with the top-level key servers (this catches everyone who copies a Claude config first).
• Both stdio (command) and Streamable-HTTP (url) work.
• Tools appear in the Copilot Chat tool picker; Copilot chooses which to call.
• OAuth 2.1 is supported for remote servers; you'll see a browser popup on first use.
• Best flow: agent mode + Plugsky MCP = 36 models available inside VS Code without leaving the editor.

How it works

Step-by-step

1. In your project root, create .vscode/mcp.json.
2. Paste this — pay attention to servers, not mcpServers:

```json

{

"servers": {

"plugsky": {

"type": "http",

"url": "https://plugsky.com/mcp",

"headers": { "Authorization": "Bearer sk-live-YOUR_KEY" }

}

}

}

```

1. VS Code shows an inline Start action. Click it.
2. Open Copilot Chat (Ctrl+Alt+I / Cmd+Shift+I).
3. Click the tools icon → check the Plugsky tools you want active.
4. Ask: "@workspace use plugsky_fusion to compare how kimi-k2 and plugsky-plus would refactor this file."

Local stdio variant

{
  "servers": {
    "plugsky-local": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@plugsky/mcp"],
      "env": { "PLUGSKY_API_KEY": "${env:PLUGSKY_API_KEY}" }
    }
  }
}

The ${env:VAR} syntax reads from your shell environment so you never commit a raw key.

Why VS Code's key is servers and not mcpServers

VS Code's MCP schema was designed alongside GitHub's Copilot extension APIs, which use servers for language-server registrations. Anthropic's reference clients (Claude Desktop) picked mcpServers to avoid collisions with existing config. The consequence: copying a Claude config into .vscode/mcp.json silently does nothing. Always double-check the top-level key when moving configs between clients.

Agent mode vs edit mode vs ask mode

Copilot Chat has three modes:

• Ask — quick Q&A, no tools invoked. MCP tools are ignored here.
• Edit — file-level edits, uses limited tools.
• Agent — full autonomous mode with all MCP tools available.

For Plugsky MCP to shine, switch to Agent mode (dropdown at the top of the Copilot Chat panel).

Copilot Business vs Enterprise for MCP

Copilot Individual technically supports MCP but tool execution is aggressive on the throttle. Business and Enterprise unlock full agent mode and higher tool-call quotas. If your team is serious about MCP, budget for Business ($19/user/mo as of Sept 2026).

Common errors and fixes

Config detected but no Start button	Top-level key is mcpServers (Claude-style)	Rename to servers
Tools don't show in picker	Server started but returned empty tools/list	Check auth scope; some tools require paid tier
"Server crashed on start"	Missing env var	Set PLUGSKY_API_KEY in shell or use ${env:...} reference
Agent mode disabled	Copilot Individual restrictions	Upgrade to Business or use Free trial
OAuth popup blocked	Browser popup blocker	Allow popups for code.visualstudio.com

Comparison — VS Code MCP vs Cursor MCP

Config key	servers	mcpServers
Requires paid subscription	✅ Copilot	⚠️ Only for Pro tier
Featured directory	GitHub Marketplace	Cursor MCP catalog
Agent mode UX	Dropdown mode toggle	Composer-native
Extension ecosystem	Massive (any VS Code ext works)	Fork of VS Code — most exts work

FAQ

Q: Why isn't my MCP server showing up in VS Code?

A: Nine times out of ten, you used mcpServers (Claude-style) instead of servers (VS Code style). Rename the top-level key.

Q: Can I use MCP in VS Code without Copilot?

A: Not with the built-in Copilot Chat. But the Continue.dev and Cline VS Code extensions both support MCP independently.

Q: Does Plugsky MCP work in Copilot Individual?

A: Yes, but with reduced tool-call quotas. Business or Enterprise recommended.

Q: How do I use OAuth 2.1 with a VS Code MCP?

A: Add "type":"http" and omit headers.Authorization. VS Code detects .well-known/oauth-protected-resource and opens a browser login on first use.

Q: Can I run the same .vscode/mcp.json config on my whole team?

A: Yes — check the file into git. Use ${env:...} references for secrets so each developer's own env supplies the key.

Trust & sources

• Author: Mustafa Hasan.
• Last updated: {DATE}.
• References: VS Code MCP docs, Copilot Chat.
• Related: [Add MCP to Cursor](/blog/add-mcp-to-cursor) · [Add MCP to Windsurf and Zed](/blog/add-mcp-to-windsurf-zed) · [Best MCP servers 2026](/blog/best-mcp-servers-2026).