How to add Claude Debugs For You to Claude Desktop
Let any LLM interactively debug your code in VS Code via breakpoints and expression evaluation. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.
Last updated June 14, 2026 · 509★ · stdio · no auth
Claude Desktop config for Claude Debugs For You
{
"mcpServers": {
"claude-debugs-for-you": {
"command": "node",
"args": [
"/path/to/mcp-debug.js"
]
}
}
}Setup steps
- 1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
- 2Paste the Claude Debugs For You config below under the top-level "mcpServers" key.
- 3Fill in any placeholder secrets (API keys, paths) in the snippet.
- 4Save the file, then fully quit and reopen Claude Desktop.
- 5Open a chat and confirm Claude Debugs For You's tools appear under the 🔌 tools menu.
Before you start
- Visual Studio Code with the "Claude Debugs For You" extension installed (from GitHub Releases or the VS Code Marketplace)
- Node.js (the stdio server runs via `node mcp-debug.js`)
- A project with a `.vscode/launch.json` configured to debug the target file (e.g. using `${file}`)
- An MCP client that supports tool use (Claude Desktop, Continue, Cursor, etc.)
What Claude Debugs For You can do in Claude Desktop
listFilesList all files in the workspace (optionally filtered by include/exclude glob patterns). Used to find requested files.
getFileContentGet file content with line numbers for a given absolute path. Typically used after listFiles to understand available files.
debugExecute a debug plan made of steps: setBreakpoint, removeBreakpoint, launch, continue, and evaluate. Breakpoints support an optional condition; expressions are evaluated in the current paused stack frame. Breakpoints must be set before launching or while paused; launch brings you to the first breakpoint, and continue advances between breakpoints.
Security
Distributed as a VS Code extension (from GitHub Releases or the VS Code Marketplace), not via npm. The stdio config requires the absolute path to the generated `mcp-debug.js`; obtain it with the VS Code command "Copy MCP Debug Server stdio path to clipboard" and substitute it for `/path/to/mcp-debug.js`. The server gives the LLM the ability to read workspace files, set/launch breakpoints, and evaluate arbitrary expressions in your running program's debug context, so only enable it on code you trust to execute.
Claude Debugs For You + Claude Desktop FAQ
Where is the Claude Desktop config file?
Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Claude Debugs For You config there under the "mcpServers" key and restart the client.
Is Claude Debugs For You safe to use with Claude Desktop?
Distributed as a VS Code extension (from GitHub Releases or the VS Code Marketplace), not via npm. The stdio config requires the absolute path to the generated `mcp-debug.js`; obtain it with the VS Code command "Copy MCP Debug Server stdio path to clipboard" and substitute it for `/path/to/mcp-debug.js`. The server gives the LLM the ability to read workspace files, set/launch breakpoints, and evaluate arbitrary expressions in your running program's debug context, so only enable it on code you trust to execute.
Does it only work with Claude?
No. It is an MCP server, so it works with any tool-capable LLM/client. The author demonstrates it with Claude Desktop and Continue, and documents SSE setup for clients like Cursor.
What languages are supported?
It is language-agnostic, as long as the language has debugger console support and you provide a valid `.vscode/launch.json` for debugging the target file in VS Code.
How do I configure it for Claude Desktop?
Install the VS Code extension, run the command "Copy MCP Debug Server stdio path to clipboard", then add an `mcpServers` entry named e.g. `debug` with `command: "node"` and `args: ["/path/to/mcp-debug.js"]` (the copied path) to your `claude_desktop_config.json`, and restart the client.