How to Actually Debug Your Vibe Coded App I’ve been trying out...
Prajwal Tomar@PrajwalTomar_
57 views
Jun 25, 2025
~2 min read
Advertisement
1
How to Actually Debug Your Vibe Coded App
I’ve been trying out Cursor + Sentry’s MCP server for a while and LOVED it
👇
I’ve been trying out Cursor + Sentry’s MCP server for a while and LOVED it
👇
2
1/ Hit a weird production bug last week
One of the client features stopped working silently
No toast
No crash
Just a broken flow with no visible error
Checked logs → found an undefined value where a user ID was expected
But couldn’t reproduce it locally
One of the client features stopped working silently
No toast
No crash
Just a broken flow with no visible error
Checked logs → found an undefined value where a user ID was expected
But couldn’t reproduce it locally
3
2/ I plugged in the Sentry MCP server inside Cursor
Took 1 min:
• Add the MCP server URL in settings
• Authenticate with your Sentry account
• Save it
Now I could paste any Sentry issue URL into Cursor and just ask what’s wrong
Took 1 min:
• Add the MCP server URL in settings
• Authenticate with your Sentry account
• Save it
Now I could paste any Sentry issue URL into Cursor and just ask what’s wrong
4
3/ I dropped the issue link into Cursor and typed:
“Can you trace what’s causing this issue and suggest a fix?”
That’s it. No screenshot. No stack trace dumping.
Cursor + MCP took over.
“Can you trace what’s causing this issue and suggest a fix?”
That’s it. No screenshot. No stack trace dumping.
Cursor + MCP took over.
5
4/ It did the full diagnosis inside Cursor
• Pulled full context from Sentry (user info, stack trace, env)
• Traced the error back to a missing return inside an async function
• Showed me the exact place the value was getting lost
• Even explained why it wasn’t triggering a visible error
I would’ve spent hours just getting here manually
• Pulled full context from Sentry (user info, stack trace, env)
• Traced the error back to a missing return inside an async function
• Showed me the exact place the value was getting lost
• Even explained why it wasn’t triggering a visible error
I would’ve spent hours just getting here manually
6
5/ I asked it to patch the function
It added the missing return, added fallback logic for edge cases, and annotated the code
Then I ran a quick CodeRabbit review:
• Security check
• API safety
• General refactor suggestions
All inside Cursor
It added the missing return, added fallback logic for edge cases, and annotated the code
Then I ran a quick CodeRabbit review:
• Security check
• API safety
• General refactor suggestions
All inside Cursor
7
6/ Deployed and tested it live
Triggered the same flow in production → worked perfectly
Sentry logs cleared
No more undefined
Feature worked as expected
From bug to fix in under 20 minutes
Triggered the same flow in production → worked perfectly
Sentry logs cleared
No more undefined
Feature worked as expected
From bug to fix in under 20 minutes
8
7/ Why this workflow changes debugging for solo devs
Before:
• Switch tabs
• Manually follow stack traces
• Google random errors
• Guess + test
Now:
• Paste issue link into Cursor
• Get the diagnosis
• Ship the fix with confidence
Zero context switching
Before:
• Switch tabs
• Manually follow stack traces
• Google random errors
• Guess + test
Now:
• Paste issue link into Cursor
• Get the diagnosis
• Ship the fix with confidence
Zero context switching
9
9/ Final takeaway
If you’re using Sentry and building with Cursor
Please connect the MCP server and try it once
You’ll:
• Stop jumping between logs and code
• Get faster, more accurate bug fixes
• Actually enjoy debugging again
Bookmark this and set it up next time you ship something
If you’re using Sentry and building with Cursor
Please connect the MCP server and try it once
You’ll:
• Stop jumping between logs and code
• Get faster, more accurate bug fixes
• Actually enjoy debugging again
Bookmark this and set it up next time you ship something
