Operations | Monitoring | ITSM | DevOps | Cloud

What is a Session Replay? Record video-like user-sessions to debug your app. Sessions Replays show you what happened and when, along with providing you with all of the relevant logs and traces to debug a user issue without them ever needed to write in.

Lets be real, who really knows whats happening inside MCP Server? Well, now you can! We've been building our MCP Server for the past few months, and we've taken all the tools that we've used to debug it and turned them into a set of observability tools to help you monitor your MCP servers end to end.

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.

Build an MCP server starting from 0 using Vercel's Next.js template, and ends in generating hot takes in the tone of David Cramer. Scaffold Sentry, add tool calls via Cursor CLI, and setup MCP monitoring with Sentry's new wrapMcpServerWithSentry method.

Replays in Sentry are awesome. With one property in your Sentry config you can start capturing video-like replays of user interactions with your application, but the problem is... you still have to watch them... but not anymore! AI replay summaries take your replays and run the events through an LLM to summarize the events that happened in them. They are broken up into chapters, with the breadcrumb sequences embedded in, so you can quickly get context of whats happening in every replay.