Sentry

Why use it

Key features

• Hosted HTTP endpoint: https://mcp.sentry.dev/mcp
• OAuth sign-in for the hosted connection
• Organization/project URL scoping is supported

Example replay

Illustrative saved transcript; historical tool calls and timings are not current API documentation or a live execution.

What it looks like in practice

Install

Cursor: remote HTTP + OAuth

{
  "mcpServers": {
    "sentry": {
      "url": "https://mcp.sentry.dev/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http sentry https://mcp.sentry.dev/mcp

Complete the client OAuth flow on first connection. Optionally append /{organizationSlug}/{projectSlug} to scope the endpoint.

Self-hosted: local stdio alternative

npx @sentry/mcp-server@latest --host=sentry.example.com

Set SENTRY_ACCESS_TOKEN in the process environment. The official local setup lists org:read, project:read, project:write, team:read, team:write and event:write scopes; this is not a read-only token recipe. Select appropriate skills and follow the upstream setup for your deployment.

Client/version scope: Cursor / Claude Code HTTP. Other clients: pending verification.

Use Cases

Suggested prompts, not measured outcomes. Installation and listed tools were reviewed; these workflows were not executed.

Triage a fresh production incident in 5 minutes

What's the top new issue in our `web-prod` project in the last hour, ranked by event count?

Get the latest event for that issue. Show me the stacktrace, the release, and the last 5 breadcrumbs before the crash.

Was this issue first seen in the same release as it appeared, or did it carry over? Compare the release tag.

Cross-reference Sentry errors with the GitHub commits that caused them

For Sentry issue `WEB-3a91`, list every release where it appeared and the event count per release.

For the 3 releases with the highest event count, use the GitHub MCP to get the commit diff. What files did each release change?

Based on those diffs, what's the most likely root cause? Be specific — point to the line(s).

Generate a weekly engineering quality report from Sentry data

For our org, give me crash-free session % per project for this week vs last week. Flag any project where it dropped.

What 5 issues are responsible for the most events this week, across all projects?

Based on this data, what should the team prioritize fixing next week? Consider both volume and user impact.

Quantify the user impact of a known bug before deciding to fix

For Sentry issue `WEB-3a91`, how many unique users have hit it in the last 30 days, and what % of total active users is that?

Among affected users, what's the distribution by browser, OS, and account tier (paid vs free)?

Rank our top 10 open bugs by users-affected this month. Where does this one sit?

Combinations

Integration compatibility: pending verification. Treat these as suggested workflows.

Issue WEB-3a91 spiked after release [email protected]. Find the commits in that release on GitHub, identify the most likely culprit, and draft a revert PR.

Find any new Sentry issues from the last 24h with >100 events. For each, create a Linear bug ticket assigned to the on-call engineer.

Pull this week's Sentry stats and create a Notion page in the Engineering / Weekly Reports database.

Tools

Selected parameters checked against upstream definitions. Consult the connected server tools/list for your installed version.

• get_issue_details

  issueUrl?: string, organizationSlug?: string, issueId?: string, eventId?: string, regionUrl?: string | null; provide an issue URL or identifying issue/event context

  Inspect a known issue; other tools depend on enabled skills

Cost & Limits

api_quota: pending verification

per_call_tokens: pending verification

monetary: pending verification: see current upstream pricing and hosting requirements.

budget_tip: Limit requested data and inspect actual output before expanding queries.

Security

Hosted OAuth is managed by the client. Local stdio uses SENTRY_ACCESS_TOKEN.

Hosted requests pass through mcp.sentry.dev; self-hosted local setup uses the configured host.

Hosted: complete OAuth consent

Local stdio setup: org:read, project:read, project:write, team:read, team:write, event:write

Local documented scopes include writes; review enabled skills and consent.

CVE status and a full security audit: pending verification.

Troubleshooting

Hosted connection or authentication failure

Check HTTP transport support and finish client OAuth. Use the separate local setup for self-hosted Sentry.

Alternatives

Pending verification: alternative projects and tradeoffs have not been rechecked.

Official sources

Documentation checked 2026-10-08. No authenticated service was executed. Unchecked claims are marked pending verification.

• https://mcp.sentry.dev/ — checked 2026-10-08
• https://github.com/getsentry/toolkit — checked 2026-10-08
• https://github.com/getsentry/toolkit/blob/main/packages/mcp-core/src/tools/catalog/get-issue-details.ts — checked 2026-10-08

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills