Skip to main content
Glama
yanmxa

Multi-Cluster MCP Server

by yanmxa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Multi-Cluster MCP Server

No user-submitted related servers found.

    Related Servers

    • kube-mcp

      YoussofKhawaja
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that lets AI assistants query multiple Kubernetes clusters simultaneously using natural language.
      3
      MIT

    • Kubectl MCP Tool

      rohitg00
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Kubernetes clusters through natural language, supporting core Kubernetes operations, monitoring, security, and diagnostics.
      39 npm
      960
      MIT

    • argocd-mcp-server

      asklokesh
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for integrating ArgoCD GitOps continuous delivery tool with GenAI applications, enabling intelligent Kubernetes deployment management.
      -

    • kubeaid-mcp

      1Shubham7
      A
      license
      A
      quality
      D
      maintenance
      Exposes a Kubernetes cluster to MCP-compatible AI clients, enabling read-only and optional write operations on cluster resources like pods, deployments, and namespaces through natural language.
      9
      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.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: clusters lists clusters, connect_cluster generates access credentials, kube_executor runs kubectl commands, and prometheus queries metrics. The descriptions clearly differentiate their functions, eliminating any ambiguity for an agent.

    Naming Consistency3/5

    The naming is mixed with no consistent pattern: clusters is a noun, connect_cluster uses verb_noun, kube_executor uses a compound noun, and prometheus is a proper noun. While readable, the lack of a uniform convention (e.g., all verb_noun or all nouns) reduces predictability.

    Tool Count4/5

    With 4 tools, the count is slightly low but reasonable for a multi-cluster Kubernetes management server. It covers core operations like listing clusters, accessing them, executing commands, and monitoring metrics, though it could benefit from additional tools for more comprehensive management.

    Completeness3/5

    The toolset covers key areas (discovery, access, execution, monitoring) but has notable gaps for a multi-cluster domain, such as creating/deleting clusters, managing resources across clusters, or handling configurations. Agents can work around this for basic tasks, but advanced operations may be limited.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources