Sentry Mcp
Triage production errors, inspect Sentry issues, and debug stack traces from your AI assistant without opening the Sentry UI for every question.
Overview
io.github.getsentry/sentry-mcp is a MCP server for the Operate phase that lets AI assistants query Sentry for errors, issues, and debugging context.
What is this MCP server?
- Official @sentry/mcp-server (v0.25.0) for error monitoring, issue tracking, and debugging
- stdio transport with SENTRY_ACCESS_TOKEN user auth
- Maintained in getsentry/sentry-mcp monorepo (packages/mcp-server)
- Surfaces Sentry data to AI assistants for faster incident and bug triage
- Version 0.25.0
- npm @sentry/mcp-server
Community signal: 722 GitHub stars.
What problem does it solve?
Production exceptions pile up in Sentry while you context-switch between the IDE and the issue UI to understand stack traces and user impact.
Who is it for?
Indie developers with Sentry-instrumented apps who want agent-assisted triage during operate and late ship hardening.
Skip if: Greenfield projects with no Sentry SDK, or teams that need full incident paging and runbooks without a Sentry account.
What do I get? / Deliverables
Your agent can pull Sentry issues and debugging details through MCP so you fix bugs and stabilize releases with less tab hopping.
- Agent-accessible Sentry issue and event context
- Faster debug loops from chat without manual API scripting
- Official-maintained MCP tools aligned with Sentry API
Recommended MCP Servers
Journey fit
Sentry is canonical on the Operate shelf because live error monitoring is the core job; agents also use it in Ship during pre-release stabilization. Issue tracking and exception context map directly to the errors subphase—fixing what users actually hit in production.
How it compares
Official Sentry observability MCP, not a generic log grep skill or hosting control plane.
Common Questions / FAQ
Who is io.github.getsentry/sentry-mcp for?
Builders and small teams using Sentry who want Claude Code, Cursor, or Codex to investigate errors and issues via MCP during debugging sessions.
When should I use io.github.getsentry/sentry-mcp?
Use it when operating production or finishing ship-phase stabilization and you need fast issue context tied to code changes in the agent chat.
How do I add io.github.getsentry/sentry-mcp to my agent?
Install @sentry/mcp-server, configure stdio MCP in your agent, set SENTRY_ACCESS_TOKEN from Sentry user auth settings, then invoke Sentry tools from your session.