MCP server for querying Sentry alerts and issues.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"gfg-sentry-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Sentry MCP Server (Python) This project provides a Python MCP server with tools for: - list alerts - retrieve alert detail (including rule payload) - search issues - retrieve an issue - list issue events - retrieve issue event ## Tools 1. `sentry_list_alert_rules` - Lists issue alert rules and/or metric alert rules. 2. `sentry_retrieve_alert_rule_detail` - Retrieves a single alert rule detail (`metric` or `issue`). 3. `sentry_search_issues` - Searches issues using Sentry query syntax. - Parameters: - `query` (required): Sentry issue search query. - `org_slug` (optional): overrides `SENTRY_ORG_SLUG`. - `limit` (optional): max results, clamped to `1..100` (default `25`). - Returns: - `organization`: organization slug used. - `query`: original query string. - `count`: number of issues in this response. - `issues`: raw issue objects from Sentry. - Notes: - This tool fetches one page of results only. - For large result sets, use narrower filters and run multiple queries. 4. `sentry_retrieve_issue` - Retrieves one issue by issue ID. 5. `sentry_list_issue_events` - Lists error events for a specific issue. - Parameters: - `issue_id` (required): global Sentry issue ID. - `org_slug` (optional): overrides `SENTRY_ORG_SLUG`. - `start` / `end` (optional): ISO-8601 time range. - `stats_period` (optional): relative range like `24h`, `7d` (overrides start/end). - `environment` (optional): one or more environment filters. - `full` (optional): include full event body payload (stacktrace/context). - `sample` (optional): deterministic pseudo-random event order. - `query` (optional): Sentry event search query. - `cursor` (optional): pagination cursor from Sentry response headers. - Returns: - `organization`: organization slug used. - `issue_id`: issue ID used. - `count`: number of events in this response. - `events`: raw event objects from Se…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.