Skip to main content
Glama
vitalypanait

sentry-self-hosted-mcp

by vitalypanait

Related Servers

Alternatives to sentry-self-hosted-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      F
      maintenance
      A 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.
      11
      21
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for self-hosted Sentry instances, providing tools to query and triage issues and events, inspect stack frames, manage releases, and access raw Sentry API.
      24
      12 npm
      9
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects to Sentry.io or self-hosted Sentry instances to retrieve and analyze error reports, stack traces, and debugging information.
      2
      -
    • F
      license
      B
      quality
      F
      maintenance
      A 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.
      11
      11
      -
    • F
      license
      B
      quality
      D
      maintenance
      A 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.
      2
      22
      -
    • A
      license
      A
      quality
      A
      maintenance
      A 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.
      7
      22 npm
      847
      MIT

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have distinct purposes: list vs. get, issue vs. event vs. stacktrace. Some minor overlap exists between get_event and get_stack_frames, as both return stacktrace data, but they are differentiated by level of detail and formatting.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case. The 'get_' and 'list_' prefixes clearly indicate action type, and resource names are used uniformly across the set.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a read-only Sentry debugging workflow. Each tool provides a meaningful view into issues and events without unnecessary bloat or redundancy.

    Completeness3/5

    The tool surface covers exploration and retrieval well, including issues, events, stacktraces, and projects. However, it lacks any mutating operations (e.g., updating issue status, resolving issues) and has no way to list all events for an issue, which could create dead ends in a complete debugging workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues