Sentry MCP server

Sentry × Claude

Use the Sentry MCP server
in Claude

Query issues, releases, and errors across your Sentry projects — straight from your AI. This guide connects Sentry to Claude (claude.ai and the Claude desktop app) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · OAuth sign-in

Setup: Sentry in Claude

Claude adds MCP servers via custom connectors in Settings. The gateway route takes about two minutes:

  1. Create a free gate gateway and connect Sentry to it from the verified directory (one click).
  2. Open claude.ai → Settings → Connectors and click 'Add custom connector'.
  3. Name it 'gate' and paste your gateway URL, then approve the authorization.
  4. Ask Claude something Sentry can answer — the call runs through your gateway, with your rules applied and logged.

What to ask once it’s connected

Which issues spiked after yesterday's release?
Summarize the top unresolved errors in the checkout flow.
Find the release that introduced this regression.
Draft a post-mortem from the timeline of issue #4132.

Why route it through a gateway

One URL, every client

The same Sentry connection works in Claude Code, ChatGPT, Cursor, VS Code too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool Sentry exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything Claude did with Sentry — searchable, exportable, auditable.

Scanned and probed

Sentry passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: Sentry in Claude Code · Sentry in ChatGPT · Sentry in Cursor · Sentry in VS Code