mcp-nodejs-debugger

Up to you, but there's actually a formal logging pathway[1] in MCP that has the potential to put this message somewhere that either of the two consumers[2] of your service could see it https://github.com/hyperdrive-eng/mcp-nodejs-debugger/blob/v... 1: https://spec.modelcontextprotocol.io/specification/2024-11-0... 2: the person, and (while I don't have evidence of it) I also can't think why the LLM couldn't see the message, either

Cursor often gets into "dead loops" trying to fix code [1][2]. But, Cursor also seems to get out of dead loops when it adds `console.log` statements everywhere. We thought: "What if Cursor could access Node.js at runtime?". That would save it from adding `console.log` everywhere, and still get out of dead loops. We looked into it and got Cursor to debug Node.js on its own. It's a prototype, but if you're interested in trying it out, we'd love some feedback! Github: github.com/hyperdrive-eng/mcp-nodejs-debugger --- References: [1]: "At this point I feel like giving up on Cursor and just accept that WE'RE NOT THERE YET." ~Source: https://forum.cursor.com/t/cursor-for-complex-projects/38911 [2]: "We've all had the issue. You're trying to build a complex project with your AI companion. It runs into a dead loop, coding in circles, making sugge

Debugging is hard for LLMs, because they primarily depend on source code, and they don't have access to runtime state. I spent countless hours debugging code, and the only way I found LLMs useful for that, is to ask them to add log lines. That's annoying, because it pollutes my code and adds unnecessary diffs. So we made an MCP server that solve this problem. It gives MCP clients (like Claude Code) access to a NodeJS inspector, so they can: 1. set breakpoints 2. step in, step out, continue 3. fetch the current execution location 4. read console output 5. run JS using eval To try: 1. run a Node JS server in debug mode ``` node --inspect <file.js> ``` or ``` NODE_OPTIONS="--inspect" npm run <command> ``` 2. add the MCP to Claude Code ``` claude mcp add nodejs-debugger npx @hyperdrive-eng

Little tangent: I realized that currently LLMs can't debug because they only have access to the compile time (just code). Many bugs happen due to run time complex state. If I can make LLMs think like a productive Dev who can debug, then would they become more efficient? I started hacking a small prototype along those lines: https://github.com/hyperdrive-eng/mcp-nodejs-debugger Hoping I can avoid debug death loop where I get into this bad loop of copy pasting the error and hoping LLM would get it right this one time :)