$ claude mcp add --transport http sentry https://mcp.sentry.dev/mcp copy
Sentry’s official remote MCP server (
getsentry/sentry-mcp), hosted by Sentry.
Why it matters
Checking production errors meant opening the Sentry dashboard separately. Connect the Sentry MCP and you can read errors, stack traces, and releases — and move into root-cause analysis — without leaving Claude Code.
What you can do
Representative tasks from Sentry’s official docs:
- Surface recent errors — “What are the most common errors in the last 24 hours?”
- Read a stack trace — “Show me the stack trace for error ID abc123.”
- Correlate errors to a release — “Which deployment introduced these new errors?”
- Seer root-cause analysis — “Analyze this issue with Seer and propose a fix.”
- Natural-language event search — “Show me the most recent releases for my organization.”
Grounded in code.claude.com/docs/en/mcp and getsentry/sentry-mcp.
Key features
- Issues and events — details, stack traces, natural-language search (
get_issue_details,search_issues,search_events) - Releases, projects, teams, organizations lookup
- Seer — AI root-cause analysis and autofix (
analyze_issue_with_seer) - Docs search (
search_docs)
Setup
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
After adding, authenticate via /mcp or claude mcp login sentry.
Notes
- Remote-hosted — OAuth auth
- Local (stdio) option —
npx @sentry/mcp-server@latest --access-token=...(requires a Sentry User Auth Token) - License — FSL-1.1-Apache-2.0 (
getsentry/sentry-mcp) - A plugin path is also available —
claude plugin marketplace add getsentry/sentry-mcpthenclaude plugin install sentry-mcp@sentry-mcp