Skip to main content
VS Code configures MCP servers for Copilot in an mcp.json file.

​
Where the file lives

​
Add the connector

Then, in .vscode/mcp.json:
VS Code uses servers (Cursor uses mcpServers) and requires an explicit "type": "http". Copying a Cursor config across won’t work unchanged.
You can also run MCP: Add Server from the Command Palette and pick Workspace or Global, which writes the same file for you.

​
With a bearer token

If you shared with --bearer, prompt for the token rather than committing it:
password: true masks it as you type, and VS Code stores it for subsequent use. This matters because .vscode/mcp.json is meant to be committed.

​
Check it connected

VS Code shows each server’s status in its MCP panel. As always, the HeyMCP inspector is the definitive check — look for handshake rows fingerprinted as VS Code.

​
It’s not showing up

Check you used servers and not mcpServers, and that "type": "http" is present. Both are easy to get wrong when adapting a config from elsewhere.
VS Code never reached the edge. Check the URL and that heymcp share is still running.
The Authorization header isn’t reaching the edge, or the token doesn’t match --bearer.