VS Code Integration Guide

VS Code does not have native MCP support built-in yet. However, you can connect Proxima in seconds using popular AI extensions like **Cline** or **Continue** to activate MCP tools inside your VS Code coding workflows.

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 50+ Proxima tools (like solve, deep_search, etc.) appear in the active MCP list.

Method 2: Integration via Continue

Continue is another popular open-source coding assistant for VS Code. It uses a core configuration file to manage MCP servers:

1 Install the **Continue** extension from the Marketplace.

2 Click the gear icon at the bottom right of the Continue sidebar panel to open your global `config.json`.

3 Find the `"contextProviders"` block, or define it, and add the Proxima MCP reference:

{ "contextProviders": [ { "name": "mcp", "params": { "url": "http://localhost:3210" } } ] }

4 Save the file. Continue will automatically query Proxima's HTTP server and expose its tools inside chat queries using the `@mcp` flag.

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.