mcp-sentry
Related Servers
Alternatives to mcp-sentry
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.223-
- AlicenseBqualityFmaintenanceA 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.1121ISC

Sentry MCP Serverofficial
AlicenseBqualityDmaintenanceA 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.1112ISC- AlicenseNot 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.MIT

Sentry MCPofficial
AlicenseAqualityBmaintenanceA 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.74971Functional Source , Version 1.1, ALv2 Future- FlicenseNot gradedqualityDmaintenanceA TypeScript server that allows AI agents to access, retrieve, and analyze Sentry error data through the Modern Context Protocol.2-
TDQS
Scored across 2 tools
Both tools have nearly identical descriptions, both involving retrieving and analyzing Sentry issues. The only difference is the input parameter (project slug vs ID/URL), but the overlapping purpose and identical phrasing make it unclear which tool to use in a given scenario.
Both tools follow a 'get_' prefix with snake_case, which is consistent. However, the first tool name 'get_list_issues' is slightly awkward (could be 'get_issues_by_project') but still fits the pattern. Minor deviation from ideal naming.
With only 2 tools, the server feels underdeveloped for a comprehensive Sentry integration. While the scope is focused on retrieval, additional tools for updating or managing issues are expected. The count is borderline but not extremely low.
The tool set only covers retrieving issues by project or ID. Missing operations like updating issue status, assigning, or searching across projects create significant gaps that would hinder an agent from performing typical Sentry workflows.