Operations | Monitoring | ITSM | DevOps | Cloud

Debugging issues with Sentry's MCP

Turns out, this MCP thing is pretty solid. We've built the MCP server to tap into all the different areas of context within Sentry and make it easy to bring these into your editor client to help debug your application. Want to know the most fixable issues in your environment? Easy. Want to see your query performance for your backend? Just ask it.

It broke... lets fix it with Sentry MCP and Seer

Real debugging starts in the editor where you're probably digging through the last commits wondering what random thing changed. Fortunately, you're probably using Sentry and it's going to give you that information. Sentry's MCP is the best way to bring all that context of what broke and how, into your editor so you can fix broken things faster. With Seer, you can bring in the root cause, and solution, and have tools like Cursor or Claude Code go fix it. We'll show you how.

Sentry MCP server monitoring

We just launched MCP server monitoring in beta. You can instrument most server-side JavaScript SDK based MCP servers with one line of instrumentation code within your MCP SDK implementation using: wrapMcpServerWithSentry(McpServer) See details like protocol usage, client usage, traffic, tool usage, and performance across your MCP implementation so you you can get visibility into all the sharp edges that your MCP server has — who’s using it, how it’s working (or not), and get alerted when things break.