Retrieve details for a specific Sentry issue by ID or URL, including the stacktrace from the latest event. Supports filtering and automatic truncation to reduce response size.

List all projects within the configured Sentry organization.

List issues for a specific project, optionally filtering by query or status. Supports pagination.

List issues using Sentry search query syntax (e.g., "is:unresolved environment:production"). More powerful than list_sentry_issues which is project-scoped.

Update the status of a Sentry issue.

Add a comment to a Sentry issue.

Get the fingerprint hashes for an issue. Useful for understanding why events are grouped together.

Bulk update multiple issues at once (resolve, ignore, unresolve, assign). Useful for triaging many issues.

Retrieve details for a specific event ID within a project. IMPORTANT: For large events, always use limit parameter (e.g., limit: 10) to avoid token limits.

List all events for a specific issue. Useful to see all occurrences of an error over time.

List error events in a project. Search across all events without knowing the issue ID.

Extract structured stack trace frames from an event. Optimized for debugging.

Check if debug symbols (dSYM files) are missing for iOS/macOS crashes.

Extract all breadcrumbs from an event, showing the trail of events leading up to an error.

List releases in the organization. Releases link code deployments to error data.

Get detailed information about a release including health stats, commits, and authors.

List all teams in the organization.

List all tags captured for an issue. Tags help identify patterns (e.g., environment, OS, user segment affected).

Get tag value distribution for a specific tag key. Shows which values occur most frequently for an issue.

List activity log for an issue. Shows comments, assignments, status changes, and other events.

Get distributed trace details with full span tree and timing information. Requires Performance data.

Get the fingerprinting rules and grouping configuration for an issue. Shows why events are grouped together.

Merge multiple issues into one by fingerprint hash. Use after identifying that separate issues should be grouped together.

Make a raw API call to any Sentry endpoint. Returns unfiltered JSON. WARNING: Event endpoints can return 100K+ tokens. Use grep_pattern for events.