Skip to main content
Glama
HieuAnh87

selfhosted-sentry-mcp

by HieuAnh87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to selfhosted-sentry-mcp

No user-submitted related servers found.

    Related Servers

    • Sentry MCP Server

      javaDer
      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
      -

    • sentry-self-hosted-mcp

      vitalypanait
      A
      license
      A
      quality
      D
      maintenance
      MCP server for integrating self-hosted Sentry with AI assistants, enabling project and issue listing, issue details with stack traces, and event retrieval.
      7
      25 npm
      1
      MIT

    • Sentry MCP Server

      Pyda-AI
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A stateless FastMCP server that enables interaction with multiple Sentry instances, including US, EU, and self-hosted versions, through a single deployment. It provides tools for searching issues, events, and traces, allowing users to monitor and debug applications using natural language.
      21 npm
      MIT

    • MCP Sentry

      MCP-100
      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
      -

    • Sentry MCP Server

      codyde
      A
      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
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools target distinct resources, and the long descriptions explicitly differentiate near-neighbors (e.g. list_issues vs list_sentry_issues, list_issue_events vs list_error_events, update_sentry_issue_status vs bulk_update_issues). However, the event-fetching cluster (get_sentry_event_details, list_issue_events, list_error_events, get_stack_frames, list_breadcrumbs) still has adjacent boundaries that an agent could confuse, and single vs bulk status updates overlap.

    Naming Consistency4/5

    Names follow a mostly predictable snake_case verb_noun pattern (list_, get_, create_, update_, merge_, bulk_update_). The main blemish is an inconsistent redundant 'sentry' infix applied to only a subset (get_sentry_issue, list_sentry_projects, raw_sentry_api) while sibling tools omit it, which slightly muddies predictability.

    Tool Count3/5

    At 28 tools the surface is heavy and sits above the comfortable 3-15 range, with some redundancy (multiple issue/event listing tools). Sentry is a broad domain so most tools earn their place, but the count is borderline overweight.

    Completeness4/5

    Coverage spans issues, events, attachments, releases, traces, tags, feedback, teams, projects, grouping and comments, with a raw_sentry_api escape hatch for gaps. Missing explicit release creation and dedicated issue assignment tooling, but bulk_update_issues handles assignment and deploys are usually external, so gaps are minor.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources