Sentry MCP Observability

Quick start

• Use Sentry MCP tools only. Do not call local Python helpers, direct REST scripts, or SENTRY_AUTH_TOKEN workflows for issue/event inspection.
• Prefer issue URL input when the user provides it; MCP can extract org, project, and issue identifiers directly.
• Defaults: time range 24h, environment prod, limit 20 unless the user specifies otherwise.
• Use MCP-native issue IDs, event IDs, trace IDs, and org/project slugs when present; do not invent fallbacks.

Core tasks

1) Specific issue or URL

• Use mcp__sentry__get_issue_details for a known issue ID, event ID, or full Sentry issue URL.
• Use mcp__sentry__search_issue_events to filter events within that issue by time, environment, release, user, or trace.
• Use mcp__sentry__get_issue_tag_values for aggregate distributions such as affected URLs, browsers, environments, or releases.

2) Search across issues