Skip to main content
Glama
ACRT-EVAL
by ACRT-EVAL

Related Servers

Alternatives to mcp-server-kubernetes

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables connection to a Kubernetes cluster to list and manage pods, services, deployments, nodes, and namespaces, including creating, deleting, describing pods and retrieving logs for debugging.
      11
      10,522 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables connecting to a Kubernetes cluster to manage it, including listing pods, services, deployments, nodes, and namespaces, creating and deleting pods, describing pods, and retrieving logs for debugging.
      10,522 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects to a Kubernetes cluster through the current kubectl context and enables listing, creating, deleting, and describing pods, services, deployments, nodes, and namespaces, plus retrieving logs for debugging.
      10,522 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Connects to a Kubernetes cluster using your current kubectl context, letting an assistant list pods, services, deployments, nodes, and namespaces, create, delete, and describe pods, and pull logs for debugging. It turns everyday cluster management into natural-language tool calls.
      11
      10,522 npm
      MIT

    TDQS

    B3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action combination (list vs create vs delete vs describe on separate resources). get_logs overlaps conceptually with list/describe since it spans multiple resource types, but its purpose is clear enough to avoid misselection.

    Naming Consistency4/5

    Strong verb_noun pattern (list_pods, create_pod, delete_pod, describe_pod, list_nodes). The lone outlier is 'cleanup', which lacks a verb_noun structure and is vaguer than the rest, and get_logs uses 'get' rather than the dominant 'list'.

    Tool Count5/5

    Eleven tools is well-scoped for a Kubernetes management server, covering listing, creation, deletion, inspection, logs, and cleanup without bloat.

    Completeness3/5

    Coverage is asymmetric: deployments can be created but not deleted, and there's no describe for deployments or services despite describe_pod existing. Pods have full list/create/delete/describe/logs lifecycle, but the broader surface has notable gaps that could cause agent dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues