Sentry MCP Server for Claude

Content

Connect Claude to Sentry for comprehensive error monitoring, debugging, and application health tracking. View and analyze error reports in real-time, access detailed stack traces and context, track error trends and patterns, monitor release health and regressions, analyze performance metrics, search and filter errors, and generate automated reports—all through natural language commands. Supports OAuth authentication, environment filtering, and read-only access for secure error monitoring.

Features

• View and analyze error reports in real-time (live error monitoring)
• Access detailed stack traces and error context (full debugging information)
• Track error trends and patterns over time (error analytics)
• Monitor release health and regression detection (deployment impact)
• Analyze performance metrics and bottlenecks (APM integration)
• Search and filter errors by project, environment, or tags (advanced filtering)
• Access issue details and event data (comprehensive error information)
• Monitor error frequency and user impact (prioritization metrics)
• Advanced Sentry error tracking and performance monitoring with issue management, release tracking, and team collaboration features
• Batch operations support for efficient bulk issue operations, release management, and performance analysis with automatic rate limit handling and retry logic
• Real-time error synchronization capabilities with webhook integration support for monitoring Sentry events and triggering automated workflows

Use Cases

• Debug production errors with full context (stack traces and environment)
• Identify error patterns and root causes (trend analysis)
• Track deployment impact on error rates (release health monitoring)
• Monitor application performance metrics (APM and performance tracking)
• Generate error reports for stakeholders (automated reporting)
• Investigate specific error occurrences (event-level debugging)
• Monitor error trends across projects (multi-project monitoring)
• Prioritize errors by frequency and user impact (error triage)
• Build automated error monitoring workflows that sync external systems with Sentry for real-time issue tracking and performance optimization

Installation

Claude Code

1. Run: claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
2. Verify installation: claude mcp list
3. Test connection: claude mcp status sentry
4. Authenticate with your Sentry account (OAuth flow)
5. Grant required permissions (org:read, project:read)

Claude Desktop

1. Open Claude Desktop configuration file (see configPath below)
2. Add the Sentry server configuration with HTTP transport and URL
3. Restart Claude Desktop
4. Authenticate with your Sentry account (OAuth flow)
5. Grant required permissions (org:read, project:read)
6. Verify connection in Claude Desktop

Requirements

• Sentry account (free or paid plan)
• OAuth authentication setup (via mcp.sentry.dev)
• Network access to mcp.sentry.dev (HTTPS required)
• Understanding of Sentry concepts (organizations, projects, events, issues)
• Sentry organization membership (Member or Admin role for API access)
• Understanding of Sentry API scopes (org:read, project:read, project:write)
• Claude Desktop 0.7.0+ or Claude Code with MCP support
• Understanding of error monitoring and debugging workflows
• Understanding of Sentry rate limits and API quotas
• Optional: Sentry project access permissions (for specific project access)

Configuration

{
  "sentry": {
    "url": "https://mcp.sentry.dev/mcp",
    "transport": "http"
  }
}

Examples

What are the most common errors in the last 24 hou...

Common usage pattern for this MCP server

Ask Claude: "What are the most common errors in the last 24 hours?"

Show me the stack trace for error ID abc123

Common usage pattern for this MCP server

Ask Claude: "Show me the stack trace for error ID abc123"

Which deployment introduced these new errors?

Common usage pattern for this MCP server

Ask Claude: "Which deployment introduced these new errors?"

Find all errors affecting the checkout flow

Common usage pattern for this MCP server

Ask Claude: "Find all errors affecting the checkout flow"

Get Issue Details

Retrieve detailed information about a Sentry issue

// Get Sentry issue details
const issue = await sentry.issues.get({
  organization_slug: "org-slug",
  project_id: "project-id",
  issue_id: "issue-id",
});

Security

• OAuth authentication required for access (secure token-based auth)
• Respect data sensitivity and PII concerns (error data may contain sensitive information)
• Filter by environment (production/staging) to limit data exposure
• Use read-only access when appropriate (project:read scope)
• Rate limit monitoring (429 errors indicate rate limit hits)
• Sentry API tokens and auth tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
• Sentry auth tokens should be scoped with minimal required permissions following the principle of least privilege - regularly audit token permissions and remove unused scopes
• Sentry issue, project, and organization IDs may expose error tracking data and application information - ensure Sentry resource identifiers are kept private and not shared in public configurations
• Rate limiting and API quota management are critical for Sentry MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
• Sentry webhook configurations and payloads may contain sensitive error data and stack traces - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

API rate limit exceeded - 429 status code returned

Sentry rate limits all API requests per caller identity (not per token). Check Retry-After header for wait time in seconds. Implement exponential backoff for retries (wait time increases with each retry). Reduce request frequency by batching queries or caching results. Rate limit types include DSN limit, Global limit, Quota depletion, Spike Protection, and Internal Limit. Use webhooks instead of polling when possible. Contact Sentry support for enterprise rate limit increases. Monitor rate limit headers in API responses.

Authentication failed or insufficient project permissions

Verify Auth Token has required scopes in Sentry settings (User settings > Personal Tokens). Check token assigned to correct organization/project. Ensure user role has API access (Member or Admin role required). Common scopes needed: org:read for organization access, project:read for project access, project:write for write operations. Re-generate token if expired or revoked. Verify token not exceeded user's maximum permissions. Check organization membership in Sentry dashboard.

Project not found or access denied errors

Verify project slug matches exactly (case-sensitive). Check organization membership and project access in Sentry dashboard. Ensure Auth Token has project:read scope minimum (or project:write for write operations). Confirm project not archived or deleted. Verify token has access to the specific organization containing the project. Check project visibility settings (public vs private projects). Ensure user has appropriate role (Member or Admin) in the organization.

OAuth connection fails or token invalid

Re-authenticate at https://mcp.sentry.dev/mcp to refresh OAuth tokens. Verify OAuth app has required permissions in Sentry (check scopes: org:read, project:read). Check token not revoked in Settings > Auth Tokens. Ensure organization allows OAuth apps in security settings. OAuth tokens are organization-scoped (access only to selected organization during OAuth flow). If token expired, use refresh token to obtain new access token. Verify OAuth redirect URI matches configuration. Check browser console for OAuth errors.

Sentry MCP server authentication errors with auth tokens

Verify auth token is valid and not expired. Check token scopes match required operations. Ensure token format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

Sentry rate limit errors when processing multiple requests

Implement exponential backoff retry logic with jitter. Use Sentry API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed issue data. Sentry allows 100 requests per minute per auth token.

Sentry issue or project access denied errors

Verify auth token has access to the issue or project. Check organization permissions and team membership. Ensure auth token has required scopes (org:read, project:read) for target operations.

Sentry MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Sentry API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

• Source repositorygithub.com 2026-07-13T15:19:32-07:00
• Documentationdocs.sentry.io
• Package (SHA-256 pinned)/downloads/mcp/sentry-mcp-server.mcpb