Claude Debugs For You

aka Vibe Debugging

Enable Claude (or any other LLM) to interactively debug your code

This is an MCP Server and VS Code extension which enables claude to interactively debug and evaluate expressions.

That means it should also work with other models / clients etc. but I only demonstrate it with Claude Desktop and Continue here.

It's language-agnostic, assuming debugger console support and valid launch.json for debugging in VSCode.

Getting Started

1. Download the extension from releases or VS Code Marketplace
2. Install the extension

• If using .vsix directly, go to the three dots in "Extensions" in VS Code and choose "Install from VSIX..."

3. You will see a new status menu item "Claude Debugs For You" which shows if it is running properly (check) or failed to startup (x)

You can click this status menu for the commands available

Follow one of the options below, depending on your setup

If using stdio (classic, required for Claude Desktop)

4. Copy the stdio server path to your clipboard by searching vs code commands for "Copy MCP Debug Server stdio path to clipboard"

5. Paste the following (BUT UPDATE THE PATH TO THE COPIED ONE!) in your claude_desktop_config.json or edit accordingly if you use other MCP servers

{
  "mcpServers": {
    "debug": {
      "command": "node",
      "args": [
        "/path/to/mcp-debug.js"
      ]
    }
  }
}

6. Start Claude desktop (or other MCP client)
   1. Note: You may need to restart it, if it was already running.
   2. You can skip this step if using Continue/Cursor or other built-in to VS Code

If using /sse (e.g. Cursor)

4. Retrieve the MCP server sse address by using the "Copy MCP Debug Server sse address to clipboard" command
   1. You can just write it out server URL of "http://localhost:4711/sse", or whatever port you setup in settings.
5. Add it wherever you need to based on your client
   1. You may need to hit "refresh" depending on client: this is required in Cursor
6. Start MCP client
   1. Note: You may need to restart it, if it was already running.
   2. You can skip this step if using Continue/Cursor or other built-in to VS Code

You're ready to debug!

VS Code Debugging Documentation

Open a project containing a .vscode/launch.json with the first configuration setup to debug a specific file with ${file}.

See Run an Example below, and/or watch a demo video.

Contributing

Find bugs or have an idea that will improve this? Please open a pull request or log an issue.

Does this readme suck? Help me improve it!

Demo

Using Continue

It figures out the problem, and then suggests a fix, which we just click to apply

https://github.com/user-attachments/assets/3a0a879d-2db7-4a3f-ab43-796c22a0f1ef

How do I set this up with Continue? / Show MCP Configuration

Read the docs!