MCP integration
VS Code
Wire the prom.codes MCP servers into VS Code via .vscode/mcp.json (or an MCP-aware extension) — same JSON shape as Claude Code.
VS Code reads MCP servers from .vscode/mcp.json (or an MCP-aware extension
panel). The JSON is the same shape used everywhere — see the
Claude Code page for the full walkthrough, the API
key, and troubleshooting.
Add to .vscode/mcp.json
In your project root:
{
"mcpServers": {
"context": { "type": "stdio", "command": "npx", "args": ["-y", "@prom.codes/context-mcp@latest"], "env": { "PROMETHEUS_API_KEY": "prom_live_…" } },
"memory": { "type": "stdio", "command": "npx", "args": ["-y", "@prom.codes/memory-mcp@latest"], "env": { "PROMETHEUS_API_KEY": "prom_live_…" } },
"saver": { "type": "stdio", "command": "npx", "args": ["-y", "@prom.codes/saver@latest"] }
}
}
The same prom_live_… key unlocks both code embeddings and memory; the saver
needs no key. The workspace root and DB paths are auto-detected — don't set
them unless you mean to point at a different folder.
Reload and verify
Reload the VS Code window (Cmd-Shift-P → Developer: Reload Window), then
ask the agent to run search_code for a known symbol — you should get results
with real file paths and line ranges. Tool surface: see
MCP tools.