VS Code Debugger Proxy
Open source proxy that connects stdio-based AI assistants (like Roo Code) to the VS Code Debugger MCP Server extension. Enables debugging features for AI tools by translating stdio requests to HTTP/SSE for seamless Visual Studio Code integration.
What is VS Code Debugger Proxy?
VS Code Debugger Proxy is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to open source proxy that connects stdio-based ai assistants (like roo code) to the vs code debugger mcp server extension. enables debugging features for ai tools by translating stdio requests to http/ss...
Open source proxy that connects stdio-based AI assistants (like Roo Code) to the VS Code Debugger MCP Server extension. Enables debugging features for AI tools by translating stdio requests to HTTP/SSE for seamless Visual Studio Code integration.
This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- Open source proxy that connects stdio-based AI assistants (l
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx vs-code-debugger-mcp-server-proxyConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use VS Code Debugger Proxy
The VS Code Debugger MCP Server Proxy is an open-source stdio-to-WebSocket bridge that lets stdio-based AI assistants like Roo Code connect to the VS Code Debugger MCP Server extension. By translating stdio MCP requests into HTTP/SSE communication, it enables AI tools that cannot directly speak WebSocket to access full VS Code debugging capabilities including breakpoints, variable inspection, and step-through execution.
Prerequisites
- Node.js 18+ and npm installed
- Visual Studio Code with the VS Code Debugger MCP Server extension installed
- Roo Code or another stdio-based AI assistant configured
- Git installed for cloning the proxy repository
- Basic familiarity with VS Code extension settings
Clone and build the proxy
Clone the VS Code Debugger MCP Server Proxy repository and build the TypeScript source into the dist/ directory.
git clone https://github.com/saxxon66/VS-Code-Debugger-MCP-Server-Proxy.git
cd VS-Code-Debugger-MCP-Server-Proxy
npm install
npm run buildInstall the VS Code extension
In VS Code, install the VS Code Debugger MCP Server extension from the Extensions marketplace. This extension provides the WebSocket server that the proxy will connect to.
# In VS Code: Extensions (Ctrl+Shift+X) → search 'VS Code Debugger MCP Server' → InstallConfigure the VS Code extension transport
In VS Code settings, set the VS Code Debugger MCP Server transport type to 'websocket' and note the port it listens on. The default example uses port 10101.
# In VS Code settings (settings.json):
# "vscode-debugger-mcp-server.transport": "websocket"
# "vscode-debugger-mcp-server.port": 10101Configure your AI client to use the proxy
Add the proxy to your MCP client configuration. The proxy uses stdio transport and connects to the VS Code extension's WebSocket on the configured port. Set DEBUG to false for production use.
{
"mcpServers": {
"vs-code-debugger-proxy": {
"type": "stdio",
"command": "node",
"args": ["/path/to/VS-Code-Debugger-MCP-Server-Proxy/dist/index.js", "-p", "10101"],
"env": {
"DEBUG": "false"
}
}
}
}Verify the connection
Ensure VS Code is running with a project open and the Debugger MCP Server extension active. Then connect your AI client and verify that debugging tools are available.
VS Code Debugger Proxy Examples
Client configuration
MCP client configuration for Roo Code or similar stdio-based AI assistants to connect via the proxy on port 10101.
{
"mcpServers": {
"vs-code-debugger-proxy": {
"type": "stdio",
"command": "node",
"args": ["/path/to/VS-Code-Debugger-MCP-Server-Proxy/dist/index.js", "-p", "10101"],
"env": {
"DEBUG": "false"
}
}
}
}Prompts to try
Use these prompts in Roo Code or your AI client once the VS Code debugger proxy is connected.
- "Set a breakpoint at line 25 in src/index.ts and start debugging"
- "Step through the current function and show me the value of each local variable"
- "Inspect the call stack at the current breakpoint and explain what led here"
- "Continue execution until the next breakpoint and report any exceptions thrown"Troubleshooting VS Code Debugger Proxy
Proxy fails to connect to VS Code extension with ECONNREFUSED
Ensure VS Code is open and the VS Code Debugger MCP Server extension is enabled and active. In VS Code settings, confirm transport is set to 'websocket' and the port matches the -p argument in your proxy config (default 10101). Reload the VS Code window if the extension was just installed.
npm run build fails with TypeScript errors
Ensure you are on Node.js 18+ ('node --version'). Run 'npm install' before 'npm run build' to ensure all TypeScript dependencies including the compiler are installed. Check for any tsconfig.json path issues if the build reports module not found errors.
Port mismatch between proxy and VS Code extension
The port configured in VS Code extension settings must exactly match the -p argument passed to dist/index.js. If you changed the extension port from the default, update the args array in your MCP config accordingly. Restart both VS Code and your AI client after any port change.
Frequently Asked Questions about VS Code Debugger Proxy
What is VS Code Debugger Proxy?
VS Code Debugger Proxy is a Model Context Protocol (MCP) server that open source proxy that connects stdio-based ai assistants (like roo code) to the vs code debugger mcp server extension. enables debugging features for ai tools by translating stdio requests to http/sse for seamless visual studio code integration. It connects AI assistants to external tools and data sources through a standardized interface.
How do I install VS Code Debugger Proxy?
Follow the installation instructions on the VS Code Debugger Proxy GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with VS Code Debugger Proxy?
VS Code Debugger Proxy works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is VS Code Debugger Proxy free to use?
Yes, VS Code Debugger Proxy is open source and available under the MIT license. You can use it freely in both personal and commercial projects.
VS Code Debugger Proxy Alternatives — Similar Developer Tools Servers
Looking for alternatives to VS Code Debugger Proxy? Here are other popular developer tools servers you can use with Claude, Cursor, and VS Code.
Ecc
★ 188.2kThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Javaguide
★ 155.8kJava 面试 & 后端通用面试指南，覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发
Gemini CLI
★ 104.5kA secure MCP server that wraps the Google Gemini CLI, allowing clients to query Gemini models using local OAuth sessions without requiring an API key. It provides tools for model interaction and diagnostics with built-in protection against command in
Awesome MCP Servers
★ 87.3k⭐ Curated list of Model Context Protocol (MCP) servers - tools that extend Claude Desktop, Cursor, Windsurf, and other MCP clients with custom capabilities.
MCP Servers
★ 86.0kModel Context Protocol Servers
CC Switch
★ 77.5kA cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io
Browse More Developer Tools MCP Servers
Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up VS Code Debugger Proxy in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use VS Code Debugger Proxy?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.