Skip to main content
Glama
LZBiala

oncall-router-mcp

by LZBiala
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to oncall-router-mcp

No user-submitted related servers found.

    Related Servers

    • rootly-mcp

      WYRE-AI
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server for the Rootly incident management platform — alerts, incidents, on-call schedules
      -

    • DevHub

      MrUversky
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted operational dashboard and MCP server that catalogs runnable services and their operational context, offering a read-only MCP endpoint to list projects, service status, runbooks, and reconciliation context.
      1
      Apache 2.0

    • Cloud DevOps MCP Server

      alexcgodwin
      A
      license
      A
      quality
      A
      maintenance
      Enables AI clients to assess infrastructure-as-code deployment risk, generate incident response runbooks, review CI/CD delivery readiness, and calculate SLO error budgets through structured advisory tools. Runs locally over stdio without cloud credentials or external API calls, returning guidance for platform work, pull request review, and production readiness checks.
      12
      2,512 npm
      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

    • ocp-triage-mcp

      aasthapit
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic triage of OpenShift alerts by executing YAML-defined runbooks against an upstream OCP MCP server, collecting auditable evidence bundles for LLM interpretation.
      -
    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.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of incident routing: ownership (who_owns), escalation (escalation_path), response steps (playbook), and timing (impact_clock). There is no overlap in purpose, and the descriptions make boundaries clear.

    Naming Consistency4/5

    All tool names are lowercase snake_case and are descriptive, but the pattern varies slightly: who_owns is a question-like phrase, while the others are noun compounds. This is a minor inconsistency, but the naming remains intuitive and predictable.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped to incident routing. Each tool delivers a unique, essential capability without redundancy, making the count ideal for the domain.

    Completeness4/5

    The tool set covers the core incident routing workflow: identifying ownership, following escalation paths, accessing playbooks, and tracking escalation timing. Minor gaps like incident acknowledgment or status updates exist but are outside the router's stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources