Skip to main content
Glama
razvanmacovei

Multi Cluster Kubernetes MCP Server

by razvanmacovei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Multi Cluster Kubernetes MCP Server

No user-submitted related servers found.

    Related Servers

    • Kubernetes MCP Server

      mjrestivo16
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with Kubernetes clusters through 50 specialized tools for comprehensive cluster management. Supports both local kubectl and remote SSH-based execution for managing pods, deployments, services, and other Kubernetes resources.
      49
      MIT

    • K8s MCP

      rahul007-bit
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Kubernetes clusters through 32 specialized tools for managing resources, deployments, and services. Provides both CLI and web interfaces for real-time Kubernetes operations powered by Google Gemini.
      5
      -

    • MCP Server Kubernetes

      Abinesh0206
      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.
      4,455 npm
      MIT

    • mctl

      mctlhq
      A
      license
      B
      quality
      D
      maintenance
      AI-native control plane for Kubernetes and GitOps. Provides 30+ tools for service deployment, database provisioning, and log management via natural language.
      1
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 57 tools

    Disambiguation3/5

    Most tools are distinct, but several pairs like k8s_update_resources and k8s_set_resources_for_container have nearly identical purposes, which could cause confusion. Additionally, k8s_create_ns and k8s_create_resource overlap in creating namespaces.

    Naming Consistency2/5

    Tool names mix different patterns: some use 'get_' (k8s_get_contexts), others 'list_' (k8s_list_secret), and several are noun-only like k8s_cluster_info or verb-only like k8s_describe. The naming is inconsistent and not predictable.

    Tool Count3/5

    57 tools is high but justified by Kubernetes' complexity, covering many resource types and operations. However, some redundancy suggests the set could be streamlined, making it borderline too large.

    Completeness5/5

    The tool set covers nearly all common Kubernetes operations: CRUD for resources, rollout management, scaling, node operations, RBAC, storage, network policies, jobs, and diagnostics. Only niche features like operator management are missing.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources