How VS Code handles MCP
VS Code's Copilot harness reads MCP servers from a workspace-root `.mcp.json` or the Copilot user `mcp-config.json`. Both files use a top-level `mcpServers` object; the editor-managed `.vscode/mcp.json` format is a separate, deprecated Local-harness path.
Project or global. Project scope keeps the server with the repository; global scope makes it available in every workspace.
Copilot users who want MCP tools beside their editor.
-a vscodeWhere the MCP config lives
The installer writes this file for you. Use the paths below when you want to inspect, edit, or remove a server by hand.
.mcp.jsonWorkspace-root Copilot config, offered when chat.mcp.workspaceRootConfig.enabled is on
~/.copilot/mcp-config.jsonCopilot user config; uses $COPILOT_HOME when set
%USERPROFILE%\.copilot\mcp-config.jsonUse the user-level file for every workspace
Project paths are relative to the workspace. Global paths are per user. On Windows, ~ means your user folder; use %USERPROFILE% in Explorer or PowerShell. A project config is shared with the team; a global config is personal.
Add a remote server
Start with a server in the MCP directory, or use your provider's endpoint. The examples use https://mcp.example.com/mcp so you can see the shape; replace it with the real URL.
- 01
Find the endpoint
Open a server page and copy its hosted endpoint. Do not use a local command or an npm package name for a remote server; those are different connection types.
Open the MCP directory - 02
Run the installer
Use the project config for a repository-specific server, or the global config for every workspace. The server name becomes
examplein the config.VS Code · project# Add this to VS Code MCP settings: { "mcpServers": { "example": { "type": "http", "url": "https://mcp.example.com/mcp" } } }VS Code · global# Add this to VS Code MCP settings: { "mcpServers": { "example": { "type": "http", "url": "https://mcp.example.com/mcp" } } }If the server page says SSE instead of HTTP, add
--transport sse:SSE variant# Add this to VS Code MCP settings: { "mcpServers": { "example": { "type": "sse", "url": "https://mcp.example.com/mcp" } } }Prefer the native UI? Open
Chat: Open Customizations, selectMCP Servers, and choose Add Server. RunMCP: Add Serverfor the guided flow instead. The screenshots below show each step.
Open larger viewThe editor-managed MCP server picker. For the native Copilot configuration, use Chat: Open Customizations > MCP Servers instead.View full size The MCP server picker opens with Add Server at the top.
If the command is missing, update VS Code and run it from a trusted workspace.
Open larger viewChoose Add Server to start a new MCP configuration instead of editing the JSON by hand.View full size The transport picker opens.
If Add Server is missing, close and reopen the MCP server picker.
Open larger viewFor a hosted endpoint, choose HTTP (HTTP or Server-Sent Events).View full size The Enter Server URL prompt opens.
For a local command, choose Command (stdio) instead of HTTP.
Open larger viewPaste the provider's MCP endpoint and press Enter.View full size The URL is accepted and the server ID prompt opens.
Use the Streamable HTTP endpoint, not an SSE-only URL.
Open larger viewUse a stable server ID. That ID becomes the key in the generated MCP config.View full size The ID is accepted and the configuration target opens.
Use lowercase letters, numbers, and hyphens for the server ID.
Open larger viewChoose Workspace for a repository-scoped server, or Global for every workspace.View full size The server entry is written to the chosen config.
If no config appears, check the workspace for .mcp.json.
- 03
Authorize if the provider asks
The first connection may open a browser for OAuth. Sign in with the provider and approve only the scopes you need. If the server uses an API key, create it in the provider's dashboard and add it through the client's auth flow or config.
Never paste a provider token into a project config you will commit. Prefer the client's secret store or a user-level config for credentials.
- 04
Reload and verify
Run `Chat: Open Customizations`, select MCP Servers, and confirm the server is enabled. `MCP: List Servers` opens the available server controls.
Open larger viewThe finished project config. The server entry sits under mcpServers and stays with the repository.View full size The server appears in Chat: Open Customizations > MCP Servers and can be started.
If the server is missing, reload the window and confirm the JSON is valid.
Then ask for a task, not a tool: “Find the open issues assigned to me” or “Summarize the latest release.” The client decides which advertised tool to call.
What changes in the chat
Once the server is connected, its tools appear in the client's tool list. You still talk to the agent normally; MCP is plumbing, not a different chat interface.
“Find the customer notes mentioning the migration and summarize the blockers.”
“Create a draft page with this outline, but do not publish it yet.”
“Check the failed deployment and list the last three changes that touched it.”
“Which MCP tools do you have available for this task?”
If the agent ignores the server, check that the server is enabled and that its tools are approved. Some clients require a per-tool confirmation before the first call.
When it does not connect
The server is missing
Confirm the file exists at the path above, the JSON or TOML is valid, and you restarted the client or opened a new session.
It connects but tools are empty
Enable the server in the client's MCP UI, approve its tools, and check that the provider has not revoked your token.
OAuth keeps reopening
Remove the server from the client, revoke the app's access in the provider's account settings, then add it again.
A project server is ignored
Some clients require you to trust the folder before loading project MCP config. Trust the repository, then start a new session.
What to watch for in VS Code
- VS Code asks you to trust and start a new MCP server before its tools appear.
- Open Chat: Open Customizations > MCP Servers to add, edit, disable, or uninstall a server.
- The Copilot user `mcp-config.json` is shared with GitHub Copilot CLI, not the editor-managed `.vscode/mcp.json`.
Remove or reset the server
Remove the server when it is no longer needed, or reset it when a credential or connection state gets stuck.
- Run
Chat: Open Customizationsand select MCP Servers. - Use the server's more actions menu to disable or uninstall it.
- Delete the entry from
.mcp.jsonor~/.copilot/mcp-config.jsonif it remains.
Reload the VS Code window, then add the server again if its authentication state is stale.
Official documentation
Client behavior changes. These links are the source of truth for paths, flags, and approval behavior.