Skip to content

Latest commit

 

History

History
108 lines (74 loc) · 3.67 KB

README.md

File metadata and controls

108 lines (74 loc) · 3.67 KB

description Claude Debugs For You

Badge

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 here.

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

Getting Started

  • Download the extension from releases or VS Code Marketplace
  • Install the extension
    • If using .vsix directly, go to the three dots in "Extensions" in VS Code and choose "Install from VSIX..."
  • Open a project containing a .vscode/launch.json with the first configuration setup to debug a specific file with ${file}.
  • Execute "Start MCP Debug Server" (A popup will show that it started: copy the path to mcp-debug.js)
image
  • Paste the following (BUT UPDATE THE PATH!) 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"
      ]
    }
  }
}
  • Start Claude desktop (or other MCP client)
  • You're ready to debug
  • See Run an Example below.

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

In this example, I made it intentionally very cautious (make no assumptions etc - same prompt as below) but you can ask it to do whatever.

claude-debugger.mp4

Developing

  • Cline / Open this repo with VS Code
  • Run npm run install and npm run compile
  • Hit "run" which will open a new VSCode
    • Run the command in VS Code: "Start MCP Debug Server"
  • Otherwise same as "Getting Started applies"
  • To rebuild, npm run compile

Package

vsce package

Run an Example

Enter the prompt:

i am building `longest_substring_with_k_distinct` and for some reason it's not working quite right. can you debug it step by step using breakpoints and evaluating expressions to figure out where it goes wrong? make sure to use the debug tool to get access and debug! don't make any guesses as to the problem up front. DEBUG!

Configuration

There's a hidden env var you can use to set the port on the MCP side.

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

And similarly you may set the port on the vs code side using extensions settings or JSON:

image 
"mcpDebug.port": 4711

Short list of ideas

  • It should use ripgrep to find what you ask for, rather than list files + get file content.
  • Add support for conditional breakpoints
  • Add "fix" tool by allowing MCP to insert a CodeLens or "auto fix" suggestion so the user can choose to apply a recommended change or not.
  • Your idea here!