Creativity · MCP — client

MCP Client: Visual Studio Code

Visual Studio Code added first-class MCP support in 2025 through GitHub Copilot Chat's Agent Mode. The editor acts as an MCP client — letting Copilot or other chat providers call into any MCP server you configure — and is one of the most-used MCP clients alongside Claude Desktop and Cursor.

MCP facts

Kind: client
Ecosystem: anthropic-mcp
Language: TypeScript
Transports: stdio, http

Capabilities

Workspace-scoped .vscode/mcp.json for team-shared MCP servers
User-scoped settings for personal servers
Approval workflow for tool calls — same security model as other MCP clients

Install

Bundled with Visual Studio Code; enable Copilot Chat Agent Mode from Settings

Configuration

// .vscode/mcp.json
{
  "servers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "${workspaceFolder}"]
    }
  }
}

Frequently asked questions

Do I need Copilot to use MCP in VS Code?

VS Code's first-class MCP surface lives in Copilot Chat Agent Mode. Community extensions can also expose MCP clients without Copilot, but Copilot Agent Mode is the primary supported path.

Workspace vs user config?

.vscode/mcp.json is workspace-scoped (commits with the repo and shares with the team). User settings are for personal servers you want everywhere.

How does MCP interact with Copilot extensions?

MCP complements extensions: extensions add UI and commands, while MCP servers provide tool surfaces the agent can call. Many teams now ship both.

Sources

VS Code Copilot Agent Mode — accessed 2026-04-20
VS Code MCP Documentation — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20