VS Code
The Vike data server in .vscode/mcp.json for GitHub Copilot — type http, url, and an X-API-KEY header.
Add the server
Create .vscode/mcp.json in the workspace and reload the window:
{
"servers": {
"vike": {
"type": "http",
"url": "https://data.vike.io/mcp",
"headers": { "X-API-KEY": "YOUR_KEY" }
}
}
}Two differences from the Cursor shape are easy to miss: the top-level key is servers, not
mcpServers, and each entry carries an explicit type. That type is what selects the rest of
the entry's shape — http takes url and headers. Vike's data endpoint is a remote HTTP
service; there is no command for VS Code to launch.
The trader server is a stdio entry in this same file
vike-cli mcp is a local process, so it sits beside this one in the same servers object with
"type": "stdio", command and args, under a different name. See
Trader / VS Code.
Keep the credential out of the repository
.vscode/mcp.json sits inside the workspace, so a pasted key is one git add away from being
committed. Either add the file to .gitignore, or use VS Code's input-variable support so the
key is prompted for and stored by the editor rather than written into the file.
If a key does get committed, delete it under Account → API Keys and create a new one. ⚠ Deletion is the fix; rotating the file is not, because the old key keeps working until it is deleted — and for up to 45 seconds after, while the server's auth cache expires.
Verify
Open Copilot Chat in agent mode and ask:
Search for PEPE token using Vike
token_search costs 0 credits. Copilot's tools picker should list the Vike server; if the server
is present but its tools are not offered, they may need enabling for the conversation.
Troubleshooting
The file was edited but nothing changed. Reload the window. MCP configuration is read at startup.
The server never appears. Check the file path (.vscode/mcp.json, in the workspace root that
VS Code actually has open) and that the JSON parses — a trailing comma silently disables the
whole file, every entry in it with it.
Everything is configured and the calls fail. Test the key with the
raw HTTP tools/list call. A bad key on /mcp is HTTP 401 with a
JSON-RPC error in the body. ⚠ An unknown tool or a failed tool call is HTTP 200 with the error in the
body, so a client that only checks the status code reports success on those.