Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

by diegofornalha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP Sentry para Cursor

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
      13 npm
      1
      MIT

    • selfhosted-sentry-mcp

      HieuAnh87
      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
      27 npm
      9
      MIT

    • Sentry MCP Server

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

    • cursor-otel

      smith
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that instruments Cursor AI agent interactions with OpenTelemetry traces and logs to monitor agent turns and performance. It enables tracking of user queries, assistant responses, and tool usage through GenAI-compliant telemetry spans.
      MIT
    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

    B3.2/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific Sentry resources or actions, with clear separation between event capture, issue management, project operations, and monitoring. However, some overlap exists between 'sentry_setup_project' and 'sentry_create_project', and between 'sentry_capture_session' and 'sentry_start_session/end_session', which could cause minor confusion.

    Naming Consistency5/5

    All tools follow a consistent 'sentry_verb_noun' pattern with snake_case throughout, making them predictable and easy to parse. The naming convention is uniform across all 27 tools, with no deviations in style or structure.

    Tool Count3/5

    With 27 tools, the count is borderline high for a Sentry integration, feeling somewhat heavy compared to typical well-scoped servers (3-15 tools). While Sentry is a complex platform, this many tools may overwhelm agents and suggest potential fragmentation or redundancy in the surface.

    Completeness5/5

    The tool set provides comprehensive coverage of Sentry's core functionalities, including error/exception capture, issue management, project/release operations, performance monitoring, session tracking, and alerting. There are no obvious gaps, and the surface supports full CRUD/lifecycle workflows for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources