Sentry MCP Server

What it does (plain English)

Sentry records the errors and performance problems your live app runs into: a crash on the checkout page, a slow API call, a broken button in Safari. The Sentry MCP server (a plug-in that gives Claude a new ability) lets Claude read that information directly. It can search errors, open an issue with its stack trace, look at traces and performance data, and help triage and manage issues and projects.

Sentry describes it as “primarily designed for human-in-the-loop coding agents”: the tools are focused on debugging, not on every Sentry feature. It is hosted at https://mcp.sentry.dev/mcp.

Is it for you?

Pick it if you already send your app’s errors to Sentry and you build or fix that app with Claude. The best loop is in Claude Code: Claude reads the error in Sentry, finds the matching code in your project, and proposes a fix in the same session.

If you don’t use Sentry yet, this isn’t the starting point; you need Sentry set up in your app first so there are errors to look at.

What you can do with it

• Explain an error: “What are the top unresolved errors in my web project this week? Explain the first one in plain English.”
• Go from error to fix: “Open the latest TypeError on /checkout, find the code it points to, and suggest a fix.”
• Check performance: “Which endpoints got slower since yesterday’s release?”
• Triage: “Look at the five newest issues, tell me which look like duplicates, and suggest which to resolve first.”
• Pick which tool groups load: Sentry groups tools into skills such as inspect, triage, seer and project-management, and you can grant or hide them per connection.

How to set it up

1. Choose a scope. Sentry recommends scoping to one project when possible. Scoped URLs default tools to that org or project and hide extra discovery tools:

   • Everything: https://mcp.sentry.dev/mcp
   • One organization: https://mcp.sentry.dev/mcp/{organizationSlug}
   • One project: https://mcp.sentry.dev/mcp/{organizationSlug}/{projectSlug}

2. Claude Code:

   claude mcp add --transport http sentry https://mcp.sentry.dev/mcp/{organizationSlug}/{projectSlug}

   Replace the two slugs with yours (they appear in your Sentry URLs).

3. Sign in. All connections use OAuth. Run /mcp in Claude Code, select sentry, and link your Sentry account in the browser.

4. Plugin alternative. Sentry also ships a Claude Code plugin that adds a sentry-mcp subagent Claude delegates to when you ask about errors:

   claude plugin marketplace add getsentry/sentry-mcp
   claude plugin install sentry-mcp@sentry-mcp

5. claude.ai or Claude Desktop. Settings > Connectors > Add custom connector, and paste one of the URLs above. Sentry’s site does not give Claude-specific steps for this, so this uses Anthropic’s standard custom connector flow (Pro, Max, Team and Enterprise plans).

Watch out for

• AI search tools need an LLM provider on stdio. If you run the local npx @sentry/mcp-server version, tools like search_errors and search_issues need an OpenAI, Azure OpenAI, Anthropic or OpenRouter key; without one those tools are hidden. The hosted server is the easier route.
• Local token scopes. For the stdio version, Sentry lists the user-token scopes as org:read, project:read, project:write, team:read, team:write and event:write. That includes write access, so guard the token.
• Narrow the tools. Add ?skills=inspect,triage or ?disable-skills=seer to the URL to limit which skill groups appear.
• Self-hosted Sentry works only through the stdio version with --host=your.sentry.host, and the seer skill is dropped by default.
• Experimental mode. ?experimental=1 turns on forward-looking tool variants. Expect changes.
• Licence. The code is under the Functional Source License (FSL-1.1, converting to Apache 2.0 later), not a standard open-source licence.

Alternatives

• GitHub MCP to look at the code, commits and Actions runs behind an error.
• Linear MCP to turn a Sentry error into a tracked issue for later.
• Cloudflare API MCP or Vercel MCP for platform-level runtime logs if you don’t use Sentry.