Sentry Issues MCP
Related Servers
Alternatives to Sentry Issues MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol server that retrieves and analyzes Sentry.io issues, allowing users to inspect error reports, stacktraces, and debugging information from their Sentry account.222-
- -licenseNot gradedqualityAmaintenanceThis server provides tools to inspect error reports, stacktraces, and other debugging information from your Sentry account.90,196MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables retrieving and analyzing Sentry issues, including stacktraces and debugging information.2-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that connects to Sentry.io or self-hosted Sentry instances to retrieve and analyze error reports, stack traces, and debugging information.2-
- AlicenseAqualityDmaintenanceMCP server for integrating self-hosted Sentry with AI assistants, enabling project and issue listing, issue details with stack traces, and event retrieval.771MIT
- FlicenseBqualityDmaintenanceEnables interaction with Sentry's error tracking platform to fetch and manage issue details, events, and project information through the Sentry API.4471-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_project_events retrieves multiple events for a project, while get_single_event retrieves a single event by its URL or ID. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (get_project_events, get_single_event) with clear, descriptive names that indicate their specific functions. The naming is uniform and predictable.
With only 2 tools, the server feels too thin for a Sentry Issues domain, as it lacks essential operations like creating, updating, or listing issues, which are core to issue management workflows. This minimal set limits functionality significantly.
The tool surface is severely incomplete for Sentry Issues, covering only event retrieval. It misses critical operations such as listing issues, creating issues, updating issue status, or deleting issues, leaving agents unable to perform basic issue lifecycle tasks.