sentry-mcp
Enables Claude to query Sentry error data, trace issues, and pull release/health metrics without context switching.
Sentry's official MCP service, designed for human-in-the-loop coding agents. Runs as a remote OAuth-backed MCP at mcp.sentry.dev, or locally over stdio (npx @sentry/mcp-server@latest with a Sentry user auth token) for self-hosted Sentry. A Claude Code plugin adds a sentry-mcp subagent that Claude automatically delegates to for questions about errors, issues, traces, and performance.
- Summarize recent error spikes and affected users in a Slack post
- Query stack traces to identify common failure patterns across versions
- Check release health metrics before deploying to production
Enables Claude to query Sentry error data, trace issues, and pull release/health metrics without context switching. Reduces incident response time by letting LLMs surface root causes from your error tracking directly.
Engineering teams using Sentry for error monitoring who want to ask Claude about error patterns, stack traces, and release health without leaving their chat interface.
https://github.com/getsentry/sentry-mcp
By getsentry
How to Get It
claude plugin marketplace add getsentry/sentry-mcp && claude plugin install sentry-mcp@sentry-mcp
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Once it’s connected, paste this into Claude:
Help me summarize recent error spikes and affected users in a Slack post
Trust Signals Auto-scanned
Data & Access
Community Pulse Active
Discussed on Hacker News, Reddit
- Show HN: Slack bot with Sentry MCP for error summaries — Hacker News · 6 pts
- Connecting Claude Code to Notion and Sentry using MCP (practical walkthrough) — Reddit · 4 pts
- Sentry MCP drastically improved our response time to prod issues — Reddit · 3 pts
3 mentions across 2 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 810 GitHub stars; 63 contributors; last commit 6d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 810 GitHub stars; 63 contributors; last commit 6d ago; license no license.