Catalog / MCP servers

Sentry MCP

Lets a coding agent look up Sentry issues, stack traces, traces and releases, and run Seer root-cause analysis without leaving the editor.

Install

  1. Claude Code plugin

    claude plugin marketplace add getsentry/sentry-mcp

    Then claude plugin install sentry-mcp@sentry-mcp. Adds the hosted server (https://mcp.sentry.dev/mcp) and a sentry-mcp subagent. Sign in with OAuth.

  2. Local stdio (self-hosted Sentry)

    npx @sentry/mcp-server@latest --access-token=sentry-user-token

    Add --host=sentry.example.com for self-hosted. 0.40.0 was current when reviewed.

Sentry’s MCP server, built for human-in-the-loop coding agents rather than as full Sentry admin. Paste a Sentry URL or ask about an error, and the agent pulls the issue, events, breadcrumbs and trace. It can also run Seer, Sentry’s AI root-cause analysis.

When to use it

  • Going from “users are seeing this error” to the failing line without copying stack traces by hand.
  • Checking whether a release introduced new issues.
  • Self-hosted Sentry through the stdio transport.

Before you install

  • The license is FSL (source-available, becomes Apache-2.0 after two years), not OSI open source.
  • search_events and search_issues need an LLM provider key when you run locally. Without one, those tools are turned off.
  • Narrow the tools with ?skills= / --skills= or --disable-skills= if you only need to inspect errors.
Publisher
Sentry
Works with
Claude Code, Claude apps, Cursor, Codex, Any agent
License
FSL-1.1-Apache-2.0
Cost
Free tier, paid plans

Curated by Andrew Borden-Chisholm. Notes on building with these tools are on the blog.