BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

sentry-mcp

Connector Development Usable
Works inClaude Code Claude Cowork Claude Chat
Usable Scanned — metadata only

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.

810 starsFreeNo code needed
Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

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.

Claude Code Claude Cowork Claude Chat

https://github.com/getsentry/sentry-mcp

By getsentry

How to Get It

Option 1: Claude Desktop AppOpen the Customize panel in the sidebar → browse connectors → search and add. Works in Claude Code, Claude Cowork, and Claude Chat.
Option 2: Paste into Claude CodeCopy the command below and paste it into a Claude Code conversation. Claude will run it for you.
Command
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.

First thing to try

Once it’s connected, paste this into Claude:

Help me summarize recent error spikes and affected users in a Slack post
PrerequisitesSentry account. Stdio/self-hosted use needs a Sentry user auth token with org:read, project:read/write, team:read/write, event:write scopes. AI-powered search tools (search_events, search_issues) require an LLM provider key (OpenAI, Azure OpenAI, Anthropic, or OpenRouter); other tools work without one.CostFree

Trust Signals Auto-scanned

Stars810Contributors63Last updated2026-08-12Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-08-12 · scanner vattempted-no-data

Data & Access

Data processingPrompts sent to Anthropic API. Enterprise/Team plans exclude training.

Community Pulse Active

Discussed on Hacker News, Reddit

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

Ease of Use
2/5
Versatility
4/5
Reliability
5/5
Security
3/5
Overall score3.40 / 5.00 UsableEvaluatedAug 2026
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 810 GitHub stars; 63 contributors; last commit 6d ago; license no license.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →