Production Debugger
Four MCPs for the "what just broke in production" loop: Sentry for stack traces and release metadata, PostHog for session replays and error tracking, GitHub for the offending commit, and Vercel for the failing build and runtime logs. Goes from alert to root cause without dashboard hopping.
Use case: When an alert fires: read the Sentry issue, watch the PostHog session replay of the affected user, find the offending commit in GitHub, and check the Vercel build and runtime logs that shipped it. The agent stitches all four together instead of you tab-hopping.
“Sentry MCP connects an agent to Sentry error monitoring, letting it look up issues, read stack traces, inspect release data, and search events. — getsentry/sentry-mcp README”
What's in the stack
MCP servers and CLI tools that make up this stack, and how each one runs.
| Tool | Primary use | Kind | Stars | GitHub |
|---|---|---|---|---|
| Sentry MCP connects an agent to Sentry error monitoring, letting it look up issues, read stack traces, inspect release details, and work through debugging workflows without leaving the coding environment.. | MCP | 677 | repo | |
| PostHog's official MCP connects an agent to product analytics, feature flags, error tracking, surveys, and session replays. | MCP | 142 | repo | |
| GitHub MCP Server connects an agent to GitHub: read repos and code, manage issues and PRs, query workflow runs, review Dependabot and security findings, and interact with discussions and notifications.. | MCP | 29,550 | repo | |
| Vercel MCP Server gives an agent access to Vercel projects: inspect deployments, manage domains, view build and runtime logs, and interact with project configuration.. | MCP | 7 | repo |
Install the MCP servers
Pick the client you use. Each tab installs all 4 servers.
claude mcp add io-github-getsentry-sentry-mcp -- npx -y @sentry/mcp-server
claude mcp add --transport http io-github-posthog-mcp https://mcp.posthog.com/sse
claude mcp add --transport http io-github-github-github-mcp-server https://api.githubcopilot.com/mcp/
claude mcp add --transport http com-vercel-vercel-mcp https://mcp.vercel.comAdd to your CLAUDE.md / AGENTS.md
Paste this into your project's CLAUDE.md or AGENTS.md so the agent knows when and how to use each tool in the stack.
## Tools
- **Sentry MCP** — First stop for any production issue. Pull the affected issue by ID or search recent events; read the stack trace, release tag, and breadcrumbs before forming a hypothesis.
- **PostHog MCP** — Once you have a user or session reference from Sentry, watch the session replay and inspect events leading up to the error. Check feature flag state for that user — flag mismatches are a common cause of "works for me" bugs.
- **GitHub MCP** — With a file path and release tag in hand, locate the commit that introduced the regression. Read the PR description and recent commits in the affected file.
- **Vercel MCP** — Confirm the failing deployment ID, read its build logs, and check runtime logs for the time window of the alert. If the deployment hasn't reached production yet, say so before recommending a rollback.Why each tool is in this stack
A short rationale per tool, plus its individual install.
by getsentry · ★ 677 · MCP
Sentry's official MCP (677 stars). Issues, stack traces, release metadata, breadcrumbs, event search. The first tool an agent should reach for when a user reports something "broken in prod." Cited by Boris Cherny (Claude Code creator) as one of his three daily integrations.
claude mcp add io-github-getsentry-sentry-mcp -- npx -y @sentry/mcp-serverPostHog's official MCP (142 stars). Pairs with Sentry: where Sentry tells you a stack trace, PostHog tells you what the user actually clicked before it failed via session replays, plus error tracking, feature flag state, and recent events.
claude mcp add --transport http io-github-posthog-mcp https://mcp.posthog.com/sseGitHub's own MCP (29,550 stars). Once you have a Sentry release identifier or a stack trace pointing at a file, GitHub MCP finds the offending commit, the PR that introduced it, and the surrounding history.
claude mcp add --transport http io-github-github-github-mcp-server https://api.githubcopilot.com/mcp/Vercel's official MCP. Build logs, runtime logs, deployment metadata. Confirms whether the regression shipped in a specific deployment and surfaces the runtime errors that may not have made it to Sentry yet.
claude mcp add --transport http com-vercel-vercel-mcp https://mcp.vercel.com
Last reviewed · Curated by stax.sh