MCP server for retrieving issues from sentry.io or self-hosted Sentry instances
Until 2026-09-25 this record combined several servers published from one repository. The others now have records of their own: mseep-mcp-sentry-custom. Checks from before that date include them.
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-sentry-custom","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.
Below is a revised and polished version of the README.md for the `mcp-sentry-custom` project, formatted properly for clarity, correctness, and professionalism. It adheres to standard Markdown conventions and organizes the content into logical sections. --- # mcp-sentry-custom: A Sentry MCP Server ## Overview `mcp-sentry-custom` is a Model Context Protocol (MCP) server designed to retrieve and analyze issues from [Sentry.io](https://sentry.io) or self-hosted Sentry instances. This server provides tools to inspect error reports, stack traces, and other debugging information directly from your Sentry account. ## Features ### Tools 1. **`get_sentry_issue`** - **Description**: Retrieve and analyze a specific Sentry issue by its ID or URL. - **Input**: - `issue_id_or_url` (string): The Sentry issue ID or full URL to analyze. - **Returns**: Detailed issue information, including: - Title - Issue ID - Status - Level - First seen timestamp - Last seen timestamp - Event count - Full stack trace 2. **`get_list_issues`** - **Description**: Retrieve and analyze a list of Sentry issues for a specific project. - **Input**: - `project_slug` (string): The Sentry project slug. - `organization_slug` (string): The Sentry organization slug. - **Returns**: A list of issues with details, including: - Title - Issue ID - Status - Level - First seen timestamp - Last seen timestamp - Event count - Basic issue information ### Prompts 1. **`sentry-issue`** - **Description**: Retrieve formatted issue details from Sentry for use in conversation context. - **Input**: - `issue_id_or_url` (string): The Sentry issue ID or URL. - **Returns**: Formatted issue details. ## Installation ### Installing via Smithery To install `mcp-sentry-custom` for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@javaDer/mcp-sentry-custom): ```bash npx -y @smit…
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.