Sentry MCP server: setup, auth, production

What is the Sentry MCP server?

A Sentry MCP server implements the Model Context Protocol and exposes Sentry's capabilities as typed tools an agent can discover and call in the middle of a task. Error tracking and performance monitoring for applications.

Observability systems are the highest-value, lowest-risk first MCP connection: an agent that can read your metrics, traces, and logs debugs alongside you instead of asking you to paste graphs. Keep it strictly read-only and the blast radius is near zero.

A real Sentry workflow

While fixing a bug, the agent reads the exact Sentry issue — stack trace, breadcrumbs, the release it first appeared in, how many users it hit — and writes the fix against the real failure instead of a reproduction it guessed at.

What an agent can do with Sentry

• Have an agent triage the newest unresolved issues
• Pull the stack trace and breadcrumbs for a specific error while fixing it
• Find which release introduced a regression

Read-only is the right default: let the agent observe and reason first, then grant specific write actions deliberately — each behind audit logging and, for anything high-impact, human approval.

Setting up the Sentry MCP server

Use a Sentry auth token scoped to the specific projects the agent should read. Event payloads routinely contain PII, so redact or restrict before the agent ingests them.

Auth: Sentry auth token with project-scoped read access. Credentials belong in the environment or a secret store — never in the repo or the agent's sandbox. Wiring a server into Claude Code or Cursor is the same for every tool; the step-by-step lives in the MCP connection guide.

The risk to watch with Sentry

Breadcrumbs and event context leak PII readily. The scoping decision here is as much a privacy control as an access one — assume anything in an event body will end up in the model’s context.

More broadly, a production-grade Sentry integration needs scoping tokens to specific projects and redacting PII in event payloads. The MCP security checklist applies to every integration — we build servers with these controls baked in.