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
      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,601 npm
      MIT
    • 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,601 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,601 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,601 npm
      MIT

    TDQS

    B3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target clearly distinct Kubernetes resources and actions, such as list_pods vs list_deployments vs create_pod. The only mild ambiguity is cleanup, which could overlap conceptually with delete_pod if 'managed resources' includes pods created by the server.

    Naming Consistency4/5

    The set mostly follows a predictable verb_noun pattern: list_pods, create_pod, delete_pod, describe_pod, get_logs. cleanup is the main deviation because it uses a single vague verb without a resource noun.

    Tool Count5/5

    With 11 tools, the server is well-scoped for common Kubernetes inspection and basic pod/deployment operations. Each tool has a reasonably clear place and the count is neither thin nor bloated.

    Completeness3/5

    The surface covers listing core resources, creating pods/deployments, deleting pods, describing pods, logs, and cleanup. However, it lacks obvious lifecycle operations such as deleting deployments/services, updating or scaling deployments, and describing deployments/services, which limits common Kubernetes workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues