This MCP server proxy enables AI tools that communicate over stdio to connect to the VS Code Debugger MCP Server, which operates over HTTP or SSE. The proxy sits between the stdio-based client and the main VS Code debugger extension, translating stdio messages into a format the extension can understand and relaying responses back in stdio. To use it, install the main VS Code Debugger MCP Server extension (which provides the debugging capabilities) and run the proxy as a stdio MCP Server in your Roo Code or compatible MCP-enabled tool. The proxy requires the extension to be configured to use a websocket transport, and the proxy itself to listen on a specific port that the extension also targets.

Once running, configure your AI assistant or integration to connect through this proxy by specifying a stdio MCP Server entry similar to the example below. The entry points the proxy to the compiled index.js and passes a port for the websocket bridge. Ensure the port you configure in both the proxy and the VS Code extension settings matches exactly, and that the main extension is installed in your VS Code environment.

Notes:

• The proxy’s command is node and it loads the compiled server script (dist/index.js).
• The -p flag indicates the port used for the websocket bridge to the VS Code Debugger MCP Server extension.
• The VS Code extension’s Transport Type must be set to websocket in its settings to enable communication through the proxy.

Prerequisites:

• Node.js and npm installed on your machine
• VS Code Debugger MCP Server extension installed in VS Code

Installation steps:

1. Clone the repository: git clone https://github.com/your-username/vscode-debugger-mcp-server-proxy.git cd vscode-debugger-mcp-server-proxy

2. Install dependencies: npm install

3. Build the project (if applicable): npm run build

   This should produce dist/index.js (or adjust to your build output)

4. Run the proxy (example):

   Ensure the path to the built index.js is correct for your environment

   node dist/index.js -p 10101

5. Configure the MCP client to connect to the proxy port (e.g., 10101) and ensure the VS Code extension is set to websocket transport.

Optional:

• Create an MCP config entry (as in mcp_config) to permanently run the proxy via your MCP manager.

Tips and notes:

• Make sure the port configured in the proxy (-p) matches the port configured in the VS Code Debugger MCP Server extension settings (Transport Type = websocket).
• Use an absolute path to dist/index.js in your MCP configuration to avoid path resolution issues.
• If you encounter connectivity issues, verify that the VS Code extension is installed and that its websocket transport is enabled, then check firewalls or network restrictions between the proxy and the extension host.
• You can set environment variables (e.g., DEBUG) to control logging or feature flags in the proxy as needed.
• If you update the proxy, remember to rebuild the dist output and restart the MCP configuration.