Skip to main content
Glama
Vibe-Code-Agent

sentry-investigator

by Vibe-Code-Agent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to sentry-investigator

No user-submitted related servers found.

    Related Servers

    • mcp-sentry

      elliottlawson
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to retrieve and analyze Sentry issues, including error reports, stacktraces, and debugging information from Sentry.io.
      6 npm
      1
      MIT

    • Sentry MCP Server

      elad12390
      A
      license
      A
      quality
      D
      maintenance
      Enables searching and analyzing Sentry issues, events, and traces via natural language, providing tools for error investigation and distributed tracing.
      4
      MIT

    • MCP Sentry Analyzer

      RanRuan
      F
      license
      Not graded
      quality
      D
      maintenance
      Integrates Sentry error monitoring with AI-powered analysis to automatically capture frontend JavaScript errors and provide intelligent repair suggestions through multiple AI models including OpenAI, Claude, and Gemini.
      -

    • Mida MCP Server

      quyensatoru
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI to automatically perform Root Cause Analysis for app issues (e.g., sessions not recording, heatmap empty, replica drift) by querying logs, MongoDB, Shopify, and rendering rrweb replays.
      -
    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 7 tools

    Disambiguation3/5

    The set has two tools for creating Jira tickets from Sentry issues (create_jira_from_sentry and create_jira_ticket) that are nearly identical in purpose, causing ambiguity. Additionally, analyze_stack_trace and investigate_issue have some overlap in context analysis, though not exact duplicates.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern, but 'create_jira_from_sentry' introduces a preposition, and the two Jira creation tools use different naming structures despite similar functions, leading to inconsistency.

    Tool Count5/5

    With 7 tools covering Sentry issue retrieval, analysis, and Jira ticket creation, the count is well-scoped for the server's purpose without being too sparse or bloated.

    Completeness3/5

    The tools cover the primary workflow of investigating Sentry issues and creating Jira tickets, but there are minor gaps such as missing updates to tickets or listing Jira projects, and redundancy reduces overall completeness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources