Skip to main content
Glama
BenedatLLC

Kubernetes Tools MCP Server

by BenedatLLC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Kubernetes Tools MCP Server

No user-submitted related servers found.

    Related Servers

    • k8s-readonly-mcp

      ziyuyu23
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for inspecting Kubernetes clusters, allowing LLMs to list resources, describe pods, and read logs without mutation.
      5
      MIT

    • platform-mcp-server

      kamroy
      F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that exposes Kubernetes platform state (tenants, pods, SLOs, ArgoCD applications, chaos schedules, and catalog services) to AI agents, enabling natural language queries about cluster health and configuration.
      6
      -

    • 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

    • Kubernetes Monitor

      vlttnv
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for Kubernetes that allows querying cluster information and diagnosing issues through natural language interfaces like Claude.
      8
      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

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific Kubernetes resources and operations. The tools are well-differentiated by resource type (deployments, pods, services, nodes, namespaces) and action type (summaries, logs, events, specs), with no overlapping functionality that would cause confusion.

    Naming Consistency5/5

    All tools follow a consistent 'verb_noun' pattern with snake_case throughout. The naming convention is perfectly uniform with 'get_' prefix for all retrieval operations followed by specific resource identifiers, making the tool set highly predictable and readable.

    Tool Count5/5

    With 9 tools, this server is well-scoped for Kubernetes operations. Each tool earns its place by covering essential read-only operations for core Kubernetes resources (pods, deployments, services, nodes, namespaces), providing comprehensive monitoring capabilities without being overwhelming.

    Completeness3/5

    For a Kubernetes monitoring/read-only server, the coverage is good but has notable gaps. While it provides excellent read operations for core resources, there are no tools for creating, updating, or deleting resources, and missing operations like scaling deployments or executing commands in pods limit agent capabilities for full Kubernetes management.

    Maintenance

    ActivityNo data
    ResponsivenessUnresponsive

    Resources