VS Code · MCP setup
Use any MCP server in VS Code Copilot -
workspace-portable.
VS Code with GitHub Copilot speaks MCP via agent-mode tool calls. Configure 1Server once at the user level and your tools follow you across every workspace.
About VS Code
VS Code is Microsoft's flagship code editor. With GitHub Copilot's agent mode, it speaks MCP via `mcp.json` - note that VS Code's config block is `servers`, not `mcpServers`, and each entry needs an explicit `type: "stdio"`.
By Microsoft. Visit homepage
60-second install
One-click install
VS Code supports direct install - we’ll open it for you and prefill the config.
{
"servers": {
"1server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"1server-mcp-engine"
],
"env": {
"ONESERVER_API_KEY": "your-api-key"
}
}
}
}Add to your user-level mcp.json (or .vscode/mcp.json per workspace). Note the `servers` shape and the explicit `type: "stdio"` - that's VS Code's MCP convention, not the standard `mcpServers` shape.
Replace your-api-key / YOUR_KEY with the API key from your dashboard.
Why use 1Server with VS Code?
- Workspace-portable - the 1Server config lives once, applies everywhere.
- Vault keeps tokens out of `.vscode/` and away from accidental commits.
- Hot reload servers without restarting the editor.