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.

Before you start: Proxima's MCP entry point (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.

1 Open the Command Palette and run MCP: Add Server, or create .vscode/mcp.json by hand.
2 Add the Proxima entry and save:
{ "servers": { "proxima": { "type": "stdio", "command": "node", "args": [ "C:/path/to/proxima/src/mcp/index.js" ] } } }
3 Start the server from the inline Start action that VS Code shows above the entry, then open Chat in Agent mode. MCP tools are offered to the agent there, so they will not appear in plain Ask mode.
Why two formats? VS Code's own file uses 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:

1 Install the Cline extension from the VS Code Extensions Marketplace.
2 Open the Cline sidebar panel, and click on the Settings (Gear Icon) button in the top right.
3 Click Configure MCP Servers. This will open the global settings file cline_mcp_settings.json in VS Code.
4 Paste the following configuration block into the file and save:
{ "mcpServers": { "proxima": { "command": "node", "args": [ "C:/path/to/proxima/src/mcp/index.js" ] } } }
5 The Cline panel will reload, and you will see all 41 Proxima tools (like 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.

1 Install the Continue extension from the Marketplace.
2 In your project, create the file .continue/mcpServers/proxima.yaml. (Continue also accepts MCP blocks inside its main config.yaml.)
3 Add Proxima as a stdio server:
name: Proxima version: 0.0.1 schema: v1 mcpServers: - name: proxima type: stdio command: node args: - C:/path/to/proxima/src/mcp/index.js
4 Reload the window. Continue lists MCP tools in Agent mode, so open the Continue panel, switch to Agent, and ask it to call list_available_models to confirm the connection.
Note: older guides, including earlier versions of this page, describe a 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 node command is registered in your system PATH variables. If not, replace "command": "node" with the absolute path to your node binary.