Sentry MCP Server

✓ verified

Retrieve and analyze issues from Sentry.io.

Don't have ToolPiper? We'll take you to the download.

Open repository →

Publisher

Anthropic Reference (archived)

License

MIT

Transport

Local subprocess

Tools

1

What this server does

You see a Sentry link in Slack or PagerDuty, paste the issue ID into chat, and the model pulls the trace and starts on root cause. That is the workflow this server is built for, and the surface is deliberately narrow to match. One tool, `get_sentry_issue`, which accepts an issue ID or a full Sentry URL and returns title, status, level, first/last seen timestamps, event count, and the full stack trace. A matching prompt called `sentry-issue` is registered for hosts that surface prompts as slash commands. The real value shows up when the chat also has your codebase context via a filesystem or git server, because then 'stack trace from Sentry plus source on disk' is something the model can reason about as one picture. Without local code context, the trace alone is half the story. The server runs against the Sentry REST API. The auth token needs `project:read`; that is enough to fetch issue details and events. No write scope means no resolving issues, no muting alerts, no creating projects from chat. The token can be passed as `--auth-token` on the command line or as the `SENTRY_AUTH_TOKEN` env var. The upstream Anthropic reference is archived. Sentry now publishes an official, much broader MCP server at getsentry/sentry-mcp that supports issue CRUD, search, and project management. Switch when you need anything beyond reading a single issue.

Tools included

  • get_sentry_issue

    Fetch details and stack trace for a Sentry issue.

The authoritative list comes from the server's tools/list at runtime. This catalog entry may lag the upstream until the next ToolPiper release.

Install in ToolPiper

ToolPiper handles the JSON configuration. Click Install, fill in any required tokens, and the server is ready in your chat.

Don't have ToolPiper? We'll take you to the download.

Install in another client

Install in another MCP client (Claude Desktop, Cursor, Continue, Cline)

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json.

{
  "mcpServers": {
    "sentry": {
      "command": "uvx",
      "args": [
        "mcp-server-sentry",
        "--auth-token",
        "${SENTRY_AUTH_TOKEN}"
      ]
    }
  }
}

Example prompts

  • "Pull Sentry issue 1234567 and tell me which frame in the trace is most likely the cause."

  • "Look up https://sentry.io/organizations/acme/issues/789012/ and explain the error."

  • "How many events fired for issue 1234567, and over what window?"

  • "Read the trace for issue 1234567 and compare it to auth.service.ts on this branch."

Security notes

The auth token is a Sentry internal-integration token with `project:read`. Treat it as a password and revoke at docs.sentry.io/account/auth-tokens if it leaks. Read-only by design, so an attacker with the token cannot resolve issues or create projects, but they can read every error and stack trace in your Sentry account. That often includes source paths, request bodies, and PII the original code happened to log. Rotate periodically. The Anthropic reference is archived; the official getsentry/sentry-mcp replacement is more capable and actively maintained.

Related tools