arthurgousset

Thanks for sharing, first time I hear about sprkl.dev

Thanks for sharing all these links, super handy! I really appreciate it.

> “can you find all the tickets related to profile editing and combine them into an epic?”

That's a great use case. I imagine that makes you more productive because you can get multiple related issues out of the way by spending time in the same corner of your code base.

What other MCPs or use cases have caught your attention ?

Good point, I haven't used Cline yet. It looks like it can access console logs [1]

  > 4. Browser Integration
  >   * Test web pages
  >   * Capture screenshots
  >   * Inspect console logs

[1]: https://docs.cline.bot/exploring-clines-tools/cline-tools-gu...

Oh cool, thanks for sharing! I like how your VS Code extension also adds the usual debugging cues like the red dot, the yellow line, and the call stack.

> LLMs can not only add tons of log statements fast but parse the large output from a program faster.

Absolutely valid point, LLMs probably have an easier time adding log statements to the source code and parsing output from the console.

The debugger connection is "better" in certain cases because: 1. It avoids unnecessary diffs related to log statements. Currently, LLMs seem good at adding code, but forget to or struggle to delete code. 2. It avoids making logs noisy, although, admittedly, this can be managed with appropriate severity levels. 3. It provides more precise control over the program execution flow by stepping into, stepping over, and stepping out of lines.

Oh neat, thanks so much for sharing. I was getting MCP client errors when simply using `console.error`. Sending log message from the MCP server to the MCP client via the logging capability makes a ton of sense!

  ```
  {
    "capabilities": {
      "logging": {}
    }
  }
  ```

Thanks for sharing!

> Asking it to focus on 1 error at a time massively improves the success rate.

Out of curiosity, how do you tell Cursor about the bug? Do you copy/paste console messages from the terminal into the prompt?

Thanks for sharing!

> When I hit an error or exception, I explicitly tell the agent to pause and first figure out the best way to debug and quickly pinpoint the root cause.

Out of curiosity, how do you tell Cursor about the bug? Do you copy/paste console messages from the terminal into the prompt?

Oh good point, I didn't realise Console Ninja [1] is a product. Thanks for sharing!

[1]: https://console-ninja.com

Thanks for the detailed write-up, this is super useful! I really appreciate it.

> Claude captures all the NPM commands from the package json into the instructional file

Oh neat, I didn't know that. I'll try to use `/init` next time!

> it kept trying to run `npm run dev` which spins up the app itself. That's... not ideal since I'm running it myself so it can hot-reload

+1 I regularly notice that behaviour too. I'm running node in dev mode, then Cursor wants to run node, but the port is already in use.

> I'd be curious about is if there is a "clientside browser" MCP

Great point, I noticed this is a common feature request for front-end development. I haven't used it myself, but multiple people mentioned BrowserTools [1]. I think it can read the Dev Tools console, but I'm not sure about multimodal or access to the DOM.

[1]: https://github.com/AgentDeskAI/browser-tools-mcp

Oh great question, we should look into other runtimes like bun, deno, etc.

Would you like to use it in a bun project?

OP here, long-time lurker, first-time poster.

I agree with you, I also saw quite a few MCP posts on Show HN recently.

I didn't understand what the whole MCP thing was about, so my buddy and I hacked on this idea out of curiosity.

I almost didn't post it on Show HN, I thought "Ah no, nobody cares. It'll just disappear among the other posts".

Woke up Sunday morning, discovered the post is on the homepage of HN.

Re JSON-RPC, I don't have a lot to add to the conversation. I'll look into the MCP JSON-RPC spec though!

Oh interesting, thanks for sharing! First time I hear about the `CLAUDE.md` file. Catching transpilation errors seems like a great use of custom instructions.

Do you have any other custom instructions in there?

Not affiliated with Cursor, but I think there is a free plan to try Cursor out. It's still a bit janky in my opinion, but it's an interesting new dev experience.

Yes! Cursor really wants to debug. Personally, I don't love when Cursor adds 100s of `console.log` diffs to my project. I like debuggers for that.

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 suggestions it already tried that didn't work." ~Source: https://www.reddit.com/r/ChatGPTCoding/comments/1gz8fxb/solu...