claude-debugs-for-you

Claude Debugs For You is an MCP server that lets Claude (or other LLMs) interactively debug and evaluate expressions inside your code through a VS Code-integrated workflow. The server exposes a debugging-oriented toolchain that can be wired into clients like Claude Desktop or Continue, enabling step-by-step evaluation, breakpoints, and expression evaluation during debugging sessions. The extension and MCP setup are designed to be language-agnostic as long as your debugger supports the necessary console or launch.json configuration.

Use it by configuring an MCP client to connect to the server (for example via the stdio path or via an SSE endpoint). The README provides two common setup patterns: a stdio-based path for Claude Desktop and an SSE-based URL for clients like Cursor. Once connected, you can issue a debug-oriented workflow to inspect variables, run breakpoints, and apply fixes suggested by the model within your codebase.

Prerequisites:

• Node.js (recommended LTS) and npm installed
• VS Code installed (and optionally the Claude extension framework described in the MCP docs)
• Access to the MCP server project (the claude-debugs-for-you repository)

Installation steps:

1. Install dependencies and build the project (from the repository root): npm install npm run compile

2. Start the MCP server locally (example using the standard npm script flow):

   • Ensure you have a path to the MCP server script (mcp-debug.js) available
   • Run the server with Node, for example: node /path/to/mcp-debug.js
   • If you rely on the provided npm scripts, you may also use: npm run install npm run compile (and then start the server per your environment)

3. Connect an MCP client (Claude Desktop, Continue, or Cursor) using the configured server endpoint. If using stdio, configure the server path as shown in the readme: { "mcpServers": { "debug": { "command": "node", "args": ["/path/to/mcp-debug.js"] } } }

Prerequisites notes:

• Ensure the Node.js process has access to the mcp-debug.js script path and any required permissions to bind to the ports you plan to use.
• If using an IDE-based workflow (VS Code), ensure the MCP extension ecosystem settings align with the server’s connection method (stdio or SSE).

Tips and common considerations:

• The server supports both stdio (for Claude Desktop) and SSE-based setups (for Cursor/other clients); choose the method that fits your workflow.
• If you see MCP connection errors, verify the path to mcp-debug.js and ensure the client is pointing to the correct endpoint (stdio path or SSE URL).
• When testing across multiple VS Code windows, Claude Debugs For You can be handed off between windows; you can also disable autostart if you want manual control.
• The configuration examples in the readme include a sample MCP configuration for Continue; adapt the mcpServers entry to your environment if you use a different path or transport.
• Environment variables are optional but can be added as needed; use placeholders to document required variables for your deployment.