Sentry MCP Server
Related Servers
Alternatives to Sentry MCP Server
No user-submitted related servers found.
Related Servers
FlicenseBqualityFmaintenanceA Model Context Protocol server that lets AI assistants interact with the Sentry API to retrieve and analyze error data, manage projects, and monitor application performance.1111-- 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-

Sentry MCPofficial
AlicenseAqualityAmaintenanceA remote Model Context Protocol server acting as middleware to the Sentry API, allowing AI assistants like Claude to access Sentry data and functionality through natural language interfaces.736 npm867MIT- AlicenseAqualityFmaintenanceConnect AI assistants to Sentry for error tracking, issues, releases, events, and project management through the Model Context Protocol. Provides tools to list organizations, projects, issues, events, releases, teams, and members, as well as get details and update issue status.1238 npmMIT
- AlicenseNot gradedqualityDmaintenanceA TypeScript server that allows AI agents to access, retrieve, and analyze Sentry error data through the Modern Context Protocol.38 npm2MIT
- AlicenseAqualityDmaintenanceMCP server for integrating self-hosted Sentry with AI assistants, enabling project and issue listing, issue details with stack traces, and event retrieval.713 npm1MIT
TDQS
Scored across 11 tools
Most tools have distinct purposes targeting different resources like projects, issues, events, replays, and errors, with clear boundaries. However, 'get_sentry_event' and 'list_issue_events' could be slightly confusing as both relate to issue events, though the former retrieves a specific event while the latter lists events, which is clarified in descriptions.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'create_project', 'list_projects', 'get_sentry_issue', and 'search_errors_in_file'. There are no deviations in naming conventions, making the set predictable and easy to parse.
With 11 tools, the count is well-scoped for a Sentry monitoring and debugging server. It covers core operations like project management, issue and event retrieval, error searching, and setup without feeling excessive or insufficient for the domain.
The tool surface provides strong coverage for monitoring and debugging in Sentry, including CRUD-like operations for projects and issues, event listing, error searching, and setup. A minor gap is the lack of tools for updating or deleting resources, such as updating issue status or deleting projects, but agents can still perform key workflows effectively.