MCP server for retrieving issues from sentry.io
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":"mcp-server-sentry","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.
# mcp-server-sentry: A Sentry MCP server ## Overview A Model Context Protocol server for retrieving and analyzing issues from Sentry.io. This server provides tools to inspect error reports, stacktraces, and other debugging information from your Sentry account. ### Tools 1. `get_sentry_issue` - Retrieve and analyze a Sentry issue by ID or URL - Input: - `issue_id_or_url` (string): Sentry issue ID or URL to analyze - Returns: Issue details including: - Title - Issue ID - Status - Level - First seen timestamp - Last seen timestamp - Event count - Full stacktrace ### Prompts 1. `sentry-issue` - Retrieve issue details from Sentry - Input: - `issue_id_or_url` (string): Sentry issue ID or URL - Returns: Formatted issue details as conversation context ## Installation ### Using uv (recommended) When using [`uv`](https://docs.astral.sh/uv/) no specific installation is needed. We will use [`uvx`](https://docs.astral.sh/uv/guides/tools/) to directly run *mcp-server-sentry*. ### Using PIP Alternatively you can install `mcp-server-sentry` via pip: ``` pip install mcp-server-sentry ``` After installation, you can run it as a script using: ``` python -m mcp_server_sentry ``` ## Configuration ### Usage with Claude Desktop Add this to your `claude_desktop_config.json`: <details> <summary>Using uvx</summary> ```json "mcpServers": { "sentry": { "command": "uvx", "args": ["mcp-server-sentry", "--auth-token", "YOUR_SENTRY_TOKEN"] } } ``` </details> <details> <details> <summary>Using docker</summary> ```json "mcpServers": { "sentry": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/sentry", "--auth-token", "YOUR_SENTRY_TOKEN"] } } ``` </details> <details> <summary>Using pip installation</summary> ```json "mcpServers": { "sentry": { "command": "python", "args": ["-m", "mcp_server_sentry", "--auth-token", "YOUR_SENTRY_TOKEN"] } } ``` </details> ### Usag…
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.