<img src="./images/claude-debugs-for-you.png" width="64" height="64" alt="description" align="center"> 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
- Download the extension from releases or VS Code Marketplace
- Install the extension
- If using
.vsixdirectly, go to the three dots in "Extensions" in VS Code and choose "Install from VSIX..."
- 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
- Copy the stdio server path to your clipboard by searching vs code commands for "Copy MCP Debug Server stdio path to clipboard"
- Paste the following (BUT UPDATE THE PATH TO THE COPIED ONE!) in your
claude_desktop_config.jsonor edit accordingly if you use other MCP servers
- Start Claude desktop (or other MCP client)
- Retrieve the MCP server sse address by using the "Copy MCP Debug Server sse address to clipboard" command
- Add it wherever you need to based on your client
- Start MCP client
You're ready to debug!
[VS Code Debugging Documentation](https://code.visualstudio.com/Docs/editor/debugging)
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](https://github.com/continuedev/continue)
It figures out the problem, and then suggests a fix, which we just click to apply
Configuration:
You'll also need to choose a model capable of using tools.
When the list of tools pops up, make sure to click "debug" in the list of your tools, and set it to be "Automatic".
Troubleshooting
If you are seeing MCP errors in continue, try disabling / re-enabling the continue plugin
If helpful, this is what my configuration looks like! But it's nearly the same as Claude Desktop.
Using Claude Desktop
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.
Developing
- Clone / Open this repo with VS Code
- Run
npm run installandnpm run compile
- Hit "run" which will open a new VSCode
- Otherwise same as "Getting Started applies"
- To rebuild,
npm run compile
Package
Run an Example
Open
examples/python in a VS Code windowEnter the prompt:
Other things worth mentioning
When you start multiple vs code windows, you'll see a pop-up. You can gracefully hand-off "Claude Debugs For You" between windows.
You can also disable autostart. Then you'll just need to click the status menu and select "Start Server".
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!
<img src="./images/claude-debugs-for-you.png" width="64" height="64" alt="description" align="center"> 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
- Download the extension from releases or VS Code Marketplace
- Install the extension
- If using
.vsixdirectly, go to the three dots in "Extensions" in VS Code and choose "Install from VSIX..."
- 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
- Copy the stdio server path to your clipboard by searching vs code commands for "Copy MCP Debug Server stdio path to clipboard"
- Paste the following (BUT UPDATE THE PATH TO THE COPIED ONE!) in your
claude_desktop_config.jsonor edit accordingly if you use other MCP servers
- Start Claude desktop (or other MCP client)
- Retrieve the MCP server sse address by using the "Copy MCP Debug Server sse address to clipboard" command
- Add it wherever you need to based on your client
- Start MCP client
You're ready to debug!
[VS Code Debugging Documentation](https://code.visualstudio.com/Docs/editor/debugging)
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](https://github.com/continuedev/continue)
It figures out the problem, and then suggests a fix, which we just click to apply
Configuration:
You'll also need to choose a model capable of using tools.
When the list of tools pops up, make sure to click "debug" in the list of your tools, and set it to be "Automatic".
Troubleshooting
If you are seeing MCP errors in continue, try disabling / re-enabling the continue plugin
If helpful, this is what my configuration looks like! But it's nearly the same as Claude Desktop.
Using Claude Desktop
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.
Developing
- Clone / Open this repo with VS Code
- Run
npm run installandnpm run compile
- Hit "run" which will open a new VSCode
- Otherwise same as "Getting Started applies"
- To rebuild,
npm run compile
Package
Run an Example
Open
examples/python in a VS Code windowEnter the prompt:
Other things worth mentioning
When you start multiple vs code windows, you'll see a pop-up. You can gracefully hand-off "Claude Debugs For You" between windows.
You can also disable autostart. Then you'll just need to click the status menu and select "Start Server".
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!