Sentry MCP Server

MCP Server Configuration

Copy
{
  "mcpServers": {
    "sentry": {
      "command": "npx",
      "args": ["-y", "@sentry/mcp-server"],
      "env": {
        "SENTRY_AUTH_TOKEN": "<your-auth-token>",
        "SENTRY_ORG": "<your-org-slug>"
      }
    }
  }
}

Available Tools

Tool	Description
list_projects	List all projects in your Sentry organization
list_issues	List issues with filters (resolved, unresolved, etc.)
get_issue	Get detailed information about a specific issue
get_issue_events	Get individual error events for an issue
get_event	Get full event details including stack trace
list_error_events	List error events with filters
list_transaction_events	List performance transaction events
search_issues	Search issues with Sentry's query syntax
resolve_issue	Mark an issue as resolved
assign_issue	Assign an issue to a team member

Setup

1. Generate an auth token at https://sentry.io/settings/account/api/auth-tokens/
2. Required scopes: project:read, event:read, org:read, issue:read, issue:write
3. Find your org slug in your Sentry URL: https://sentry.io/organizations/<org-slug>/
4. Replace both placeholders in the configuration

Debugging Workflow

1. Ask Claude: "Show me the top unresolved issues in the backend project"
2. Drill into an issue: "Get the latest events for issue BACKEND-1234"
3. Analyze the stack trace and suggest a fix in your codebase
4. Apply the fix and resolve the issue - all within Claude Code

Security Notes

• Auth tokens grant read access to error data which may contain sensitive information (user data, request payloads)
• Use tokens with minimal scopes required
• Store tokens in .claude/settings.local.json and gitignore it
• Error events may contain PII - be mindful when sharing Claude Code sessions
• Sentry's data retention policies apply to all queried data