Sentry MCP Server
OfficialRelated Servers
Alternatives to Sentry MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityFmaintenanceA Model Context Protocol server that enables AI assistants to interact with Sentry for error tracking and monitoring, allowing retrieval and analysis of error data, project management, and performance monitoring through the Sentry API.1121-

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.732 npm921MIT- 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-
- AlicenseNot gradedqualityDmaintenanceA TypeScript server that allows AI agents to access, retrieve, and analyze Sentry error data through the Modern Context Protocol.24 npm2MIT
- FlicenseNot gradedqualityDmaintenanceA TypeScript implementation of a Model Context Protocol server that connects to Sentry error tracking service, allowing AI models to query and analyze error reports and events.6 npm-
- AlicenseAqualityDmaintenanceMCP server for integrating self-hosted Sentry with AI assistants, enabling project and issue listing, issue details with stack traces, and event retrieval.719 npm1MIT
TDQS
Scored across 11 tools
Most tools have distinct purposes, but there is some overlap between 'list_project_issues' and 'list_error_events_in_project'—both list issues/errors for a project, which could cause confusion. Other tools like 'get_sentry_event' and 'get_sentry_issue' are clearly differentiated by focusing on events vs. issues.
All tool names follow a consistent verb_noun pattern with underscores, such as 'create_project', 'list_projects', and 'get_sentry_event'. There are no deviations in naming conventions, making the set predictable and easy to understand.
With 11 tools, the count is well-scoped for a Sentry integration, covering key operations like project management, issue/event retrieval, listing, and setup. Each tool appears to serve a specific purpose without being excessive or insufficient.
The toolset provides good coverage for monitoring and debugging in Sentry, including CRUD-like operations (create, list, get) for projects, issues, and events. A minor gap is the lack of update or delete tools for issues or projects, which agents might need for full lifecycle management, but core workflows are well-supported.