Retrieve a Sentry issue by numeric ID, short ID (e.g. PROJ-1A2) or issue URL. Returns essential issue fields only; the stacktrace is NOT included unless include_latest_event is true, which adds the latest event's exception (innermost max_stack_frames frames per exception), message and recent breadcrumbs. Supports field filtering, grep and automatic truncation.

List projects in the configured Sentry organization (essential fields only). When more projects exist, the result carries a next_cursor; pass it as cursor to get the next page.

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. Returns the issue id, short ID, title and new status.

Add a comment to a Sentry issue. Returns the new comment id.

Get the fingerprint hashes for an issue (25 per page). Useful for understanding why events are grouped together. Paginate with cursor.

Bulk update issues in one project (resolve, ignore, unresolve, assign, mark seen). Scope: exactly one of issue_ids or query is required. issue_ids changes only those issues; query changes EVERY issue in the project that matches the Sentry search (up to 1000 per call). A call with neither is refused, because Sentry would otherwise change every unresolved issue in the project.

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 a distributed trace as a compact, flat list of spans/transactions (id, parent id, op, description, transaction, project, duration ms, start time, linked errors) in tree order with depth, plus totals and errors not attached to any span. Searches the last 90 days. Requires performance/tracing data.

Explain why events are grouped into an issue: takes the issue's latest event and returns its grouping breakdown — the grouping config, and per variant (e.g. app/system stack trace, fingerprint, message) whether it contributes, its hash, hint and a short summary of the contributing components. Compare hashes with get_issue_hashes.

Merge issues of the same project into one (error issues only; cross-project merges are refused). Sentry picks the surviving parent itself — the issue first seen earliest — which is not necessarily issue_id; the others become its children. The merge completes asynchronously in Sentry. Use after confirming the issues share a root cause.

List files attached to events (log files, minidumps, screenshots, view hierarchies). Pass issue_id for every attachment on an issue, or project_slug + event_id for one event. Read text attachments with get_event_attachment.

Read the contents of a text attachment (e.g. a log file) on an event. Binary attachments such as minidumps are not returned; their metadata is. Use grep_pattern to return only matching lines from large logs.

List user feedback (what end users wrote when reporting a crash) for an issue or a whole project. Pass exactly one of issue_id or project_slug. Reporter emails are omitted.

Check the Sentry connection: the user the token belongs to, the token's scopes, whether the configured organization is reachable, and which tools the scopes rule out. Call this first when other tools fail with 401/403.

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