Developer built a local MCP tool that auto-captures errors for Cursor
While (quickly iterating by letting AI write code), every crash meant the same repetitive dance: find the error in DevTools or the terminal, copy it, paste it into chat, and explain what was happening when it broke. To fix that annoyance, the developer built a small MCP server that runs in the and automatically catches errors, both server crashes and browser-side issues like a broken button or a failed fetch request.
Instead of the person explaining what happened, Cursor can simply ask the tool what broke recently. It also fires a desktop notification the moment something new breaks, so there is no more sitting around wondering why a button stopped working.
The tool is local-only, free, and requires no signup; it is published on npm as vibe-live-debugger. The project is still early-stage and the developer is looking for feedback on the approach.
Key points
- Built to remove the repetitive manual copy-paste-explain loop when debugging while
- Runs as a MCP server that s server crashes and browser errors (broken buttons, failed fetches)
- Cursor can query the tool directly instead of the developer explaining what broke
- Sends a desktop notification when a new error occurs
- Local-only, free, no signup; available on npm as vibe-live-debugger