VS Code Debugger MCP Server
Connects to the VS Code Debugger MCP Server, enabling AI assistants to interact with the VS Code debugger for debugging capabilities.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@VS Code Debugger MCP Serverset a breakpoint at line 42 in main.js"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VS Code Debugger MCP Server Proxy
This proxy acts as a bridge, enabling AI assistants that communicate via stdio to connect to the VS Code Debugger MCP Server, which uses HTTP or SSE.
Why Use This Proxy?
This tool is essential if your AI assistant does not support direct HTTP or SSE connections and requires a stdio-based server to interact with the VS Code debugger. It translates the stdio communication from your AI tool into a format the main debugger extension can understand.
Related MCP server: DebugMCP
Supercharge Your AI with the Main Extension
This proxy is a companion to the VS Code Debugger MCP Server extension. The main extension is what gives your AI its debugging superpowers.
Install it from the VS Code Marketplace
Prerequisites
Before you begin, ensure you have the following installed:
Node.js and npm: Download and install Node.js.
VS Code Debugger MCP Server: Install the main extension from the VS Code Marketplace.
Important: Extension Settings
To use this proxy, you must set the transport type of the VS Code Debugger MCP Server extension to "websocket" in the extension's settings in VS Code.
Open VS Code.
Go to Settings (
Ctrl+,).Search for VSCode Debugger MCP Server.
Set the Transport Type to
websocket.
Installation and Build
Follow these steps to get the proxy up and running:
Clone the repository:
git clone https://github.com/your-username/vscode-debugger-mcp-server-proxy.git cd vscode-debugger-mcp-server-proxyInstall dependencies:
npm installBuild the project:
npm run buildThis will compile the TypeScript source code into JavaScript in the
distdirectory.
Configuration
To connect your AI assistant, you need to configure it to use this proxy. Here is an example configuration for Roo Code:
Stdio MCP Server Config for Roo Code
Add the following to your Roo Code settings:
{
"mcpServers": {
"vscode-debugger": {
"command": "node",
"args": [
"d:/Projekte/MCP/vscode-debugger-mcp-server-proxy/dist/index.js",
"-p",
"10101"
],
"env": {
"DEBUG": "false"
},
"disabled": false,
"type": "stdio"
}
}
}Important: Make sure the path in the args array is the absolute path to the compiled index.js file on your system.
Note: The port number (10101 in the example above) must match the port configured and Transport Type is set to websocket in the VS Code Debugger MCP Server extension settings. Ensure both the proxy and the extension are set to use the same port for successful communication.
How It Works
The proxy sits between your AI assistant and the main debugger extension, translating communication between them.
License
This project is open source and licensed under the MIT License.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to debug JavaScript and TypeScript applications by connecting to Chrome DevTools Protocol-compatible debuggers, allowing them to set breakpoints, step through code, inspect variables, and evaluate expressions with full source map support.Last updated18212Apache 2.0
- Alicense-qualityDmaintenanceEnables AI agents to debug code inside VS Code by setting breakpoints, stepping through execution, inspecting variables, and evaluating expressions across multiple languages.Last updated443MIT
- Alicense-qualityFmaintenanceEnables AI assistants to interact with VS Code for language intelligence, debugging, and code execution.Last updated16MIT
- Alicense-qualityDmaintenanceEnables AI assistants to connect to browser DevTools and backend debuggers for full-stack debugging, including frontend console, network, performance, and backend log analysis.Last updated217MIT
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
Shared debugging memory for AI coding agents
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/saxxon66/VS-Code-Debugger-MCP-Server-Proxy'
If you have feedback or need assistance with the MCP directory API, please join our Discord server