Unexpected token 'D', "Debugger enabled" is not a valid JSON in Cursor IDE

[tom-voicer]

Expected Behavior

I expect the mcp server to show a green dot with no errors, and to use the tools it has to debug.

Current Behavior

When opening Cursor MCP settings and hitting "refresh", it shows a red dot with a red error:
Unexpected token 'D', "Debugger enabled" is not a valid JSON

P.S - are there any specific instructions on how to debug a Next.js back-end?

[arthurgousset]

Oh interesting, thank you so much for logging this bug! I'll look into it 🙌

[arthurgousset]

@tom-voicer I released a fix in #11 (version @hyperdrive-eng/mcp-nodejs-debugger@0.2.2).

Could you please refresh our MCP server and let me know if that fixes your error:

[arthurgousset]

P.S - are there any specific instructions on how to debug a Next.js back-end?

@tom-voicer: Great question, not yet. Are you currently working in a Next.js setup? Could you give me some context on your project and we'll give you step-by-step instructions.

I'd also happily jump on a call and pair with you on debugging your Next.js back-end. Let me a know a time that suits you or pick a slot here: https://cal.com/arthurgousset-hyperdrive/30min.

[tom-voicer]

@arthurgousset Thanks!

It's showing a green dot now with no errors :)
It seems that Cursor is aware of the MCP server and it's tools - https://i.imgur.com/NKiRaBh.png

However, it doesn't seem to actually have access to the console logs for example - https://i.imgur.com/t2I4ZgC.png

I've scheduled 30 minutes with you on Thursday.

[arthurgousset]

Thanks for sharing and for scheduling a meeting. Look forward to chatting Thursday, we can look into your setup in detail.

[arthurgousset]

I'll close this issue for now, since the original bug is fixed.