<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debugging on Vibe Coding</title><link>https://vibecoding.rest/tags/debugging/</link><description>Recent content in Debugging on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>Sentry</title><link>https://vibecoding.rest/mcp-servers/sentry/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/sentry/</guid><description>&lt;p&gt;The Sentry server gives an agent access to issues, stack traces, and event details from a Sentry project, so it can investigate a production error with the same data a human engineer would open the dashboard to see.&lt;/p&gt;</description></item><item><title>Chrome DevTools</title><link>https://vibecoding.rest/mcp-servers/chrome-devtools/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/chrome-devtools/</guid><description>&lt;p&gt;Chrome DevTools MCP connects a coding agent to a live Chrome instance, exposing the same network, console, and performance-tracing tools available in DevTools. It lets an agent navigate pages, inspect requests, read console errors, and record performance traces from inside its own workflow.&lt;/p&gt;</description></item></channel></rss>