Skip to main content
Glama
ACRT-EVAL

mcp-server-kubernetes

by ACRT-EVAL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-server-kubernetes

No user-submitted related servers found.

    Related Servers

    • mcp-server-kubernetes

      ACRT-EVAL
      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

    • Kube MCP

      icy-r
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with and manage Kubernetes clusters, supporting operations on pods, deployments, services, configmaps, secrets, namespaces, metrics, and events with built-in safety features for destructive actions.
      9
      17 npm
      1
      MIT

    • mcp-server-kubernetes

      ACRT-EVAL
      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

    • k8s-ops-mcp-server

      harish235
      F
      license
      A
      quality
      D
      maintenance
      Connects Claude Desktop to any Kubernetes cluster, enabling natural language queries for diagnostics and operations such as listing pods, viewing logs, scaling deployments, and more.
      8
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource and action (list_pods vs list_deployments vs describe_pod vs get_logs). The only mild overlaps are `cleanup` versus `delete_pod` and `get_logs` being much broader than the pod-specific read tools, but descriptions help distinguish them.

    Naming Consistency4/5

    The set follows a consistent snake_case verb_noun pattern such as list_pods, create_deployment, delete_pod, and describe_pod. `cleanup` is the only noticeable deviation as a verb-only name.

    Tool Count5/5

    Eleven tools is well-scoped for a Kubernetes MCP server, covering common read and write operations without feeling bloated. Each listed tool has a plausible place in typical cluster workflows.

    Completeness3/5

    Read coverage is decent for pods, deployments, services, namespaces, and nodes, but write coverage is thin: deployments and services have no delete/update/scale operations, and pods lack update/exec. These gaps would likely force agents to fall back to raw kubectl or fail on common lifecycle tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources