Skip to content
Back to search

claude-debugs-for-you

Enable any LLM (e.g. Claude) to interactively debug any language for you via MCP and a VS Code Extension

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/jasonjmcghee--claude-debugs-for-you/badge.svg)](/listings/jasonjmcghee--claude-debugs-for-you)

HTML

<a href="/listings/jasonjmcghee--claude-debugs-for-you"><img src="/api/listings/jasonjmcghee--claude-debugs-for-you/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Download the extension from [releases](https://github.com/jasonjmcghee/claude-debugs-for-you/releases/) or [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=JasonMcGhee.claude-debugs-for-you) 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

<details> <summary>If using stdio (classic, required for Claude Desktop)</summary>

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 </details>

<details> <summary>If using `/sse` (e.g. Cursor)</summary>

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

</details>

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](#run-an-example) below, and/or watch a demo video.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 174 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # <img src="./images/claude-debugs-for-you.png" width="64" height="64" alt="description" align="center"> Claude Debugs For You
  2. [![Badge](https://img.shields.io/badge/Visual%20Studio%20Marketplace-0.1.2-blue.svg)](https://marketplace.visualstudio.com/items?itemName=JasonMcGhee.claude-debugs-for-you)
  3. _aka Vibe Debugging_
  4. ### Enable Claude (or any other LLM) to interactively debug your code
  5. This is an [MCP](https://docs.anthropic.com/en/docs/build-with-claude/mcp) Server and VS Code extension which enables claude to interactively debug and evaluate expressions.
  6. That means it should also work with other models / clients etc. but I only demonstrate it with Claude Desktop and Continue here.
  7. It's language-agnostic, assuming debugger console support and valid launch.json for debugging in VSCode.
  8. ## Getting Started
  9. 1. Download the extension from [releases](https://github.com/jasonjmcghee/claude-debugs-for-you/releases/) or [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=JasonMcGhee.claude-debugs-for-you)
  10. 2. Install the extension
  11. - If using `.vsix` directly, go to the three dots in "Extensions" in VS Code and choose "Install from VSIX..."
  12. 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)
  13. <img width="314" alt="Screenshot 2025-03-22 at 9 51 22 PM" src="https://github.com/user-attachments/assets/2cd65e0d-4c1d-4fb6-b9ea-3995149b4043" />
  14. You can click this status menu for the commands available
  15. <img width="510" alt="Screenshot 2025-03-22 at 9 59 22 PM" src="https://github.com/user-attachments/assets/54e339e3-81f8-4ef2-a201-6742aa2c97a8" />
  16. ### Follow one of the options below, depending on your setup
  17. <details>
  18. <summary>If using stdio (classic, required for Claude Desktop)</summary>
  19. 4. Copy the stdio server path to your clipboard by searching vs code commands for "Copy MCP Debug Server stdio path to clipboard"
  20. 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
  21. ```
  22. {
  23. "mcpServers": {
  24. "debug": {
  25. "command": "node",
  26. "args": [
  27. "/path/to/mcp-debug.js"
  28. ]
  29. }
  30. }
  31. }
  32. ```
  33. 6. Start Claude desktop (or other MCP client)
  34. 1. Note: You may need to restart it, if it was already running.
  35. 2. You can skip this step if using Continue/Cursor or other built-in to VS Code
  36. </details>
  37. <details>
  38. <summary>If using `/sse` (e.g. Cursor)</summary>
  39. 4. Retrieve the MCP server sse address by using the "Copy MCP Debug Server sse address to clipboard" command
  40. 1. You can just write it out server URL of "http://localhost:4711/sse", or whatever port you setup in settings.
  41. 5. Add it wherever you need to based on your client
  42. 1. You may need to hit "refresh" depending on client: this is required in Cursor
  43. 6. Start MCP client
  44. 1. Note: You may need to restart it, if it was already running.
  45. 2. You can skip this step if using Continue/Cursor or other built-in to VS Code
  46. </details>
  47. ### You're ready to debug!
  48. _[VS Code Debugging Documentation](https://code.visualstudio.com/Docs/editor/debugging)_
  49. Open a project containing a `.vscode/launch.json` with the first configuration setup to debug a specific file with `${file}`.
  50. See [Run an Example](#run-an-example) below, and/or watch a demo video.
  51. ## Contributing
  52. Find bugs or have an idea that will improve this? Please open a pull request or log an issue.
  53. Does this readme suck? Help me improve it!
  54. ## Demo
  55. ### Using [Continue](https://github.com/continuedev/continue)
  56. It figures out the problem, and then suggests a fix, which we just click to apply
  57. https://github.com/user-attachments/assets/3a0a879d-2db7-4a3f-ab43-796c22a0f1ef
  58. <details>
  59. <summary>How do I set this up with Continue? / Show MCP Configuration</summary>
  60. [Read the docs!](https://docs.continue.dev/customize/tools)
  61. Configuration:
  62. ```json
  63. {
  64. ...
  65. "experimental": {
  66. "modelContextProtocolServers": [
  67. {
  68. "transport": {
  69. "type": "stdio",
  70. "command": "node",
  71. "args": [
  72. "/Users/jason/Library/Application Support/Code/User/globalStorage/jasonmcghee.claude-debugs-for-you/mcp-debug.js"
  73. ]
  74. }
  75. }
  76. ]
  77. }
  78. }
  79. ```
  80. You'll also need to choose a model capable of using tools.
  81. When the list of tools pops up, make sure to click "debug" in the list of your tools, and set it to be "Automatic".
  82. ### Troubleshooting
  83. If you are seeing MCP errors in continue, try disabling / re-enabling the continue plugin
  84. </details>
  85. If helpful, this is what my configuration looks like! But it's nearly the same as Claude Desktop.
  86. ### Using Claude Desktop
  87. 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.
  88. https://github.com/user-attachments/assets/ef6085f7-11a2-4eea-bb60-b5a54873b5d5
  89. ## Developing
  90. - Clone / Open this repo with VS Code
  91. - Run `npm run install` and `npm run compile`
  92. - Hit "run" which will open a new VSCode
  93. - Otherwise same as "Getting Started applies"
  94. - To rebuild, `npm run compile`
  95. ## Package
  96. ```bash
  97. vsce package
  98. ```
  99. ## Run an Example
  100. Open `examples/python` in a VS Code window
  101. Enter the prompt:
  102. ```
  103. 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!
  104. ```
  105. ## Other things worth mentioning
  106. When you start multiple vs code windows, you'll see a pop-up. You can gracefully hand-off "Claude Debugs For You" between windows.
  107. You can also disable autostart. Then you'll just need to click the status menu and select "Start Server".
  108. <img width="395" alt="Screenshot 2025-03-22 at 10 08 52 PM" src="https://github.com/user-attachments/assets/2b6d1b61-a2c6-4447-8054-b4dd02a716e8" />
  109. ## Short list of ideas
  110. - [ ] It should use ripgrep to find what you ask for, rather than list files + get file content.
  111. - [x] Add support for conditional breakpoints
  112. - [ ] 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.
  113. - Your idea here!

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.