Skip to main content
Glama

Related Servers

Alternatives to incident-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only investigation of service incidents by retrieving metrics, logs, and deployment history, and correlating evidence for root-cause analysis.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to query bundled synthetic logs, service metrics, and traces through three bounded read-only tools for evidence-first incident investigation.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to investigate incidents by listing services and dependencies, searching redacted logs, summarizing metrics, checking recent deploys, and producing ranked timelines with scoped tokens, validation, rate limiting, and audit logging.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables governed, read-only investigations of Amazon Athena access logs by searching exact user, IP, or correlation indicators and summarizing activity by correlation ID, with parameterized queries, validation, and result limits.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables natural-language investigation of Datadog data including logs, metrics, monitors, traces, hosts, dashboards, events, and incidents, all through read-only API access.
      14
      1,905 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to query application projects directly for logs, metrics, incidents, and semantic search through read-only tools.
      17
      63 npm
      1
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly distinct artifact: logs, a ticket, or a runbook. The read-only nature and ID sourcing from the incident resource further separate their roles, leaving no realistic overlap.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern: search_logs, get_ticket, get_runbook. The verb and plural/singular choices match the artifact semantics without introducing ambiguity.

    Tool Count5/5

    Three tools is lean but well within the appropriate range for a focused incident-investigation server. Each tool has a distinct, necessary role and none appears redundant.

    Completeness3/5

    The set covers read-only retrieval of logs, tickets, and runbooks, but lacks incident-level tools and any write operations such as updating tickets, commenting, or changing incident status. The incident resource helps anchor IDs, but the tool surface remains notably incomplete for full incident lifecycle work.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues