Skip to main content
Glama
yasir27uk
by yasir27uk

Related Servers

Alternatives to MCP Server Kubernetes

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive Kubernetes cluster management through kubectl operations, Helm chart deployments, pod troubleshooting, and node management. Supports both read-only and full cluster administration capabilities with built-in safety features.
      10,342 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive Kubernetes cluster management through kubectl operations and Helm chart management. Supports resource operations, logging, scaling, rollouts, and diagnostics with multiple transport modes and security features.
      -
    • 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered Kubernetes management using natural language, supporting kubectl, Helm, diagnostics, and port forwarding via MCP protocol.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables developers to manage Kubernetes workloads directly from their editor—listing pods, reading logs, scaling and restarting deployments, deleting pods, and applying configs—with secure authentication and no exposure of secret values.
      15
      MIT

    TDQS

    C2.9/5.0

    Scored across 22 tools

    Disambiguation3/5

    Most tools target distinct Kubernetes verbs or resources, but kubectl_create, kubectl_apply, and kubectl_patch overlap in resource creation/update, and kubectl_generic acts as a catch-all that duplicates every other kubectl tool. cleanup is also vaguely scoped relative to delete and uninstall operations.

    Naming Consistency3/5

    Core tools use a consistent kubectl_ prefix with snake_case, but the set mixes prefixes (helm_* and no prefix), patterns like verb_noun (install_helm_chart), noun phrases (node_management), and bare verbs (cleanup, ping). Readable but not predictable across the whole set.

    Tool Count4/5

    22 tools is on the heavy side but each covers a meaningful Kubernetes or Helm operation across resource lifecycle, node management, port forwarding, and exec. The existence of kubectl_generic makes some dedicated tools redundant, yet the count remains reasonable for the domain's breadth.

    Completeness4/5

    The surface covers core resource lifecycle (get, describe, create, apply, delete, patch, scale, rollout), Helm install/upgrade/uninstall, node management, port forwarding, exec, and context, with kubectl_generic as a fallback. Minor gaps like Helm list/rollback exist, but agents can work around most with generic commands.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues