VS Code Integration Guide
VS Code can load MCP servers natively, and extensions such as Cline and Continue have their own MCP settings. This guide covers all three routes. If you are not sure which to pick, start with the built-in method: it needs no extension, and the configuration lives in a file you can commit alongside your project.
src/mcp/index.js) forwards every tool call to the Proxima desktop app over a local port (19222 by default). Start the Proxima desktop app and log in to at least one provider (or add a BYOK key) before testing from the editor. Otherwise the server will start but tool calls will have nothing to talk to.
Method 0: Built-in MCP support (no extension)
VS Code reads MCP servers from an mcp.json file. Use .vscode/mcp.json in a workspace to share the setup with a project, or the user-level mcp.json to make Proxima available everywhere. Unlike the extension formats below, this file uses a top-level servers key (not mcpServers) and each entry needs a type.
MCP: Add Server, or create .vscode/mcp.json by hand.
servers, while Cline, Cursor, Windsurf and Claude Desktop use mcpServers. Pasting one format into the other is the most common reason a correct-looking config silently does nothing.
Method 1: Integration via Cline (Claude Dev)
Cline is one of the most popular agentic coding extensions in VS Code. It reads standard MCP configurations:
cline_mcp_settings.json in VS Code.
solve, deep_search, etc.) appear in the active MCP list.
Method 2: Integration via Continue
Continue is an open-source coding assistant for VS Code. It reads MCP servers from YAML files, one per server or group, and uses the same stdio launch fields as the other clients.
.continue/mcpServers/proxima.yaml. (Continue also accepts MCP blocks inside its main config.yaml.)
list_available_models to confirm the connection.
contextProviders entry that points Continue at Proxima's REST port. That is not how Continue loads MCP servers. Use the stdio entry above. Continue's current format is described in its MCP documentation.
3. Troubleshooting local paths
If the extension fails to connect to the node process:
- Ensure you are using forward slashes (
/) in the path arguments array on Windows (e.g.C:/path/to/Proxima/...). - Verify that the
nodecommand is registered in your system PATH variables. If not, replace"command": "node"with the absolute path to your node binary.