Wouldn't that issues list be a little less intimidating if you had some help from Sentry? We're shipping our Sentry Agent for Linear, and you can use it to call Seer and get Root Cause Analysis and Solutions back. Check it out!
It turns out, Sentry does A LOT these days. Errors, Logs, Replays, Traces, and even Agent and MCP monitoring… but all this observability works better with a good foundation. We’re going to step back to 0, and show you how to build a “not bad” Sentry implementation from the ground up.
Whether you’re building agents in your applications, or standing up an MCP server because its the new cool thing, working with AI is just different. Trying to figure out why it does the weird things it does is hard.
See how you can started using MCP Server Monitoring against your MCP Servers REALLY fast using using Sentry. One line to wrap the code, and you're good to go. Check out this video where we set it up using Vercel's mcp-handler in Next.js.
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.
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.