Sentry MCP Server: Setup Guide, Use Cases & Limitations

What Is Sentry MCP Server?

Sentry MCP Server is an MCP integration maintained by Getsentry that connects Claude to your Sentry account, enabling direct queries against error tracking data, exception analysis, and production issue debugging from within Claude Code.

Quick Facts

What You Can Do With It

• Error analysis: Pull exception details, stack traces, and error frequency data from Sentry issues directly into your Claude session.
• Production debugging: Query recent errors against a specific release or environment to correlate regressions with deployments.
• Issue triage: List and filter open issues by priority, assignee, or project to decide what to address first.
• Performance monitoring: Access transaction and performance data from Sentry to identify slow endpoints or bottlenecks.

How to Set It Up

Prerequisites: A Sentry account and an auth token with the necessary scopes (project:read, event:read, and org:read at minimum). Generate one at https://sentry.io/settings/account/api/auth-tokens/.

Step 1: Test the server locally

npx @sentry/mcp-server-sentry
**Step 2: Add it to your Claude Code config**

Open or create `.claude/mcp.json` in your project root (or `~/.claude/mcp.json` for global config) and add the following block:

```json
{
  "mcpServers": {
    "sentry": {
      "command": "npx",
      "args": ["@sentry/mcp-server-sentry"],
      "env": {
        "SENTRY_AUTH_TOKEN": "your-auth-token-here",
        "SENTRY_ORG": "your-org-slug",
        "SENTRY_PROJECT": "your-project-slug"
      }
    }
  }
}

Replace the placeholder values with your actual Sentry organization slug, project slug, and auth token. Restart Claude Code after saving.

Works Best With

Sentry MCP Server is documented as compatible with Claude Code. It follows the standard MCP server protocol, so it may work with other MCP-compatible clients, but Claude Code is the verified integration target. Use it inside an active Claude Code session where you want to pull live Sentry data while writing or reviewing code.

Known Limitations

• Authentication required: The server requires a valid Sentry auth token scoped to the correct organization and project. Misconfigured tokens are a common source of silent failures — double-check scopes before assuming the server is broken.
• Sentry API rate limits apply: All queries go through Sentry’s API, which enforces rate limits. Heavy usage in a single session may result in throttled responses.
• Self-hosted Sentry: If you run a self-hosted Sentry instance, you may need to configure the API base URL. The default targets sentry.io — check the GitHub repo for environment variable options if you are not on the managed cloud product.
• Read access only: Based on the documented use cases, this server surfaces data for analysis and debugging. Mutation operations (closing issues, updating assignments at scale) may be limited or unavailable — verify against the GitHub repo for the current tool list.
• npx cold starts: Running via npx incurs a download/cache check on first use. Pin to a specific version in your config if startup latency is a concern.

Community Resources

• GitHub repository and issues — file bugs or check existing reports against the official Getsentry repo
• Sentry community Discord — #sdk-development or general channels for integration questions
• Sentry developer documentation — reference for API token scopes, org/project slugs, and API rate limit policies