Skip to main content
Glama
jjoseph456

runner-fleet-mcp

by jjoseph456
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to runner-fleet-mcp

No user-submitted related servers found.

    Related Servers

    • Claude Ops Investigator

      Randhir123
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only Kubernetes incident investigation through MCP tools for listing pods, describing resources, fetching logs, and searching runbooks.
      1
      -

    • Autobase MCP

      PokeThePixel
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Autobase Console projects, clusters, environments, operations, PostgreSQL versions, and extensions through configurable MCP tools. Supports paginated listing and filtering, with limited redacted operation logs and no write or arbitrary execution tools.
      MIT

    • k8s-troubleshoot-mcp

      NanaGyamfiPrempeh30
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to diagnose Kubernetes clusters through read-only MCP tools, such as inspecting pod status, logs, events, nodes, deployments, and HPA metrics via natural language queries.
      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.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct concern (fleet status, SLO checks, capacity advice, incidents, cost). The main overlap is between get_slo_report (current breaches) and list_recent_incidents (recent breach reports), but descriptions clarify the temporal and evidentiary distinction.

    Naming Consistency5/5

    All names use snake_case with a clear verb_noun pattern (get_fleet_status, list_recent_incidents, recommend_runner_capacity). The verbs get/list/recommend are appropriate and consistently ordered.

    Tool Count5/5

    Five tools is well-scoped for a read-only advisory server covering fleet status, SLOs, capacity, incidents, and cost. No tool feels redundant or missing at this count.

    Completeness4/5

    The read-only advisory surface covers the main observability areas (status, SLOs, capacity, incidents, cost). Minor gaps exist for drill-down details (e.g., per-runner information or historical trends), but core agent workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources