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-sentry-fastmcp","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.
[](https://fastmcp.me/MCP/Details/1604/sentry) [](https://fastmcp.me/MCP/Details/1604/sentry) [](https://fastmcp.me/MCP/Details/1604/sentry) [](https://fastmcp.me/MCP/Details/1604/sentry) [](https://fastmcp.me/MCP/Details/1604/sentry) [](https://fastmcp.me/MCP/Details/1604/sentry) # mcp-sentry: A Sentry MCP server [](https://smithery.ai/server/@qianniuspace/mcp-sentry) ## 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 2. `get_list_issues` - Retrieve and analyze Sentry issues by project slug - Input: - `project_slug` (string): Sentry project slug to analyze - `organization_slug` (string): Sentry organization slug to analyze - Returns: 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` - Retrieve issue details from Sentry - Input: - `issue_id_or_url` (string): Sentry issue ID or URL - Returns: Formatted issue details…
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.