Skip to main content
Glama
iagogfe

mcp-allquiet

by iagogfe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-allquiet

No user-submitted related servers found.

    Related Servers

    • mcp-lab

      keyan1603
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching incidents and runbooks, retrieving incident details by URI, and creating postmortem summary prompts through MCP tools, resources, and prompts.
      MIT

    • opsgenie-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Opsgenie (Atlassian's incident/alert management and on-call platform) exposing the full public Opsgenie REST API as MCP tools.
      -

    • incidentrelay-mcp

      NikGariel
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for IncidentRelay, exposing its entire REST API (279 operations) through gateway and curated tools for on-call scheduling, alert routing, and incident management.
      MIT
    • pagerduty-mcp by PagerDuty

      pagerduty-mcpofficial

      PagerDuty
      A
      license
      B
      quality
      F
      maintenance
      Enables management of PagerDuty incidents, services, schedules, and more directly from MCP-enabled clients, with embedded interactive UIs for incident command center, on-call management, and other features.
      63
      77
      Apache 2.0
    • runframe-mcp-server by runframe

      runframe-mcp-serverofficial

      runframe
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing incident response workflows including incidents, on-call, postmortems, and more through the Runframe platform using MCP tools.
      50 npm
      4
      MIT

    • pagerduty-mcp

      chenzhaoxuan0
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.
      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

    A3.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    The generic call_read/call_write/call_delete tools overlap somewhat with the specific incident tools, but their descriptions clearly distinguish them as raw API access versus curated workflows. The incident-specific tools are distinct and well-scoped.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_operations, describe_operation, call_read, list_incidents, get_incident, create_incident, update_incident). The generic call_* tools deviate slightly but still follow a predictable verb style.

    Tool Count4/5

    10 tools is a reasonable count for an API wrapper server. The generic call_* tools plus specific incident tools create slight redundancy but the count is well within acceptable range.

    Completeness4/5

    The server covers incident lifecycle (list, get, create, update) plus on-call lookup and raw API access for anything else. Minor gaps exist (no explicit delete_incident tool) but the generic call_delete covers that.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources