Skip to main content
Glama
Portfolio-jaime

Kubernetes MCP Server

by Portfolio-jaime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Kubernetes MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • mcp-server-kubernetes

      ACRT-EVAL
      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
      3,426 npm
      MIT

    • K8s MCP Server

      apecloud
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs like Claude to securely execute Kubernetes CLI tools (kubectl, helm, istioctl, argocd) across multiple clusters through dynamic kubeconfig support, allowing natural language Kubernetes management and operations.
      5
      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
      2 npm
      1
      MIT
    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 6 tools

    Disambiguation3/5

    The three get_* tools target distinct Kubernetes concepts, but analyze_versions, compare_versions, and get_outdated_components overlap heavily around version analysis, making it easy to confuse them. Descriptions help somewhat, but the boundaries between 'analyze', 'compare', and 'outdated' are not crisply defined.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern like get_pods, get_helm_releases, and get_outdated_components. However, analyze_versions and compare_versions break the 'get_' prefix convention, introducing minor inconsistency while remaining readable and predictable.

    Tool Count5/5

    Six tools is a well-scoped number for a focused Kubernetes server. Each tool appears purposeful, and the count is within the ideal range for an agent to understand and navigate without overload.

    Completeness3/5

    The toolset covers cluster, pod, and Helm information plus version analysis, but it lacks common Kubernetes resources like deployments, services, nodes, and namespaces. It also has no mutation or upgrade operations, which may leave agents unable to act on version findings.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources