# Sentry — MCP Server

> Triage issues, stack traces and releases from chat without opening ten browser tabs.

**Source:** https://mcpplaygroundonline.com/mcp-servers/sentry  
**Transport:** http  
**Requires auth:** Yes

---

## What it does

Sentry’s MCP is aimed at on-call, engineering leads, and support engineers who need quick answers: what new errors showed up in the last release, which issue is the user-facing 500, or whether two crash groups are the same root cause. The server mirrors Sentry’s permission model, so a token that can only read a single project will not exfiltrate the rest of the org. Pair it with GitHub or Linear MCP when you need to jump from a stack trace to a PR and a Jira follow-up, all in one session.

## Tools exposed

- Search and list issues by project, environment, and time window
- Fetch event payloads and stack traces for a selected issue
- Inspect release, deploy, and commit metadata tied to a regression
- Summarise trends (volume spikes, new versus recurring) the API exposes to the tool layer

## Example queries you can run

- "What new errors appeared in production after the 14:00 UTC deploy?"
- "Summarise the top 5 issues by event volume in the web client for the last 24 hours."
- "Which issue matches this Sentry event URL, and which release first showed it?"
- "Are these two Sentry issues duplicates of the same line in `checkout.py`?"

## Details

- **Recommended model:** anthropic/claude-sonnet-4.5 — Claude Sonnet 4.5 handles stack traces, release correlation, and long error threads well. For simple “get issue 1234” fetches, Haiku 4.5 is often enough.
- **Transport:** http
- **Authentication:** Required — Sentry org auth token (Settings → Account or Organization → Auth Tokens) with at least `project:read` and `event:read` for the projects you will query.
- **Hosted endpoint:** https://mcp.sentry.dev/mcp
- **Official source:** [Sentry product documentation](https://docs.sentry.io)

## Frequently asked questions

### What is the Sentry MCP server?

It is a hosted remote MCP Sentry provides so AI tools can list and read issues, events, and related metadata in your organisation using the same security boundaries as the REST and UI APIs, instead of you copying error bodies into a chat by hand.

### How do I get a Sentry token for the MCP server?

Create a personal or organisation access token in Sentry with the minimum scopes: typically `org:read`, `project:read`, and `event:read` for error triage. Pass it as a bearer token to your MCP client, or use whatever configuration your product requires for the Authorization header.

### Can the MCP server delete issues or change alert rules?

The template and defaults in most clients focus on read-only triage. If Sentry ever exposes write tools, treat them with the same caution as write APIs: prefer read-only tokens until you explicitly need and trust automated mutations.

### Will this work with Sentry on EU data residency or self-hosted Sentry?

The hosted mcp.sentry.dev endpoint is built for Sentry’s SaaS. Self-hosted and EU-specific hosts may use different base URLs; follow your organisation’s Sentry or contractual guidance before pointing an agent at non-default regions.

### What model is best for Sentry triage in Agent Studio?

Use Claude Sonnet 4.5 for multi-issue comparisons and “what changed in this release” questions, where the model has to juggle time ranges, tags, and stack frames. You can A/B the same prompt against Haiku 4.5 in Agent Studio to see where premium reasoning pays off.

---

_Test this server across 40+ models on MCP Playground: https://mcpplaygroundonline.com/mcp-servers/sentry — free, no install._