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
      D
      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.
      7
      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

    A3.9/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target clearly distinct Kubernetes resources and levels (nodes, pods, deployments, services, logs, etc.), and the descriptions explicitly distinguish similar tools. However, get_pod_events overlaps with get_events, which can also filter by involved_kind and involved_name, creating a minor selection ambiguity.

    Naming Consistency5/5

    All tool names use snake_case with a consistent get_ prefix and resource-oriented nouns. The patterns get_<resource>_summaries, get_<resource>, and get_logs_for_<entity> are predictable and easy to scan.

    Tool Count3/5

    With 21 tools, the set is on the heavy side for a read-only inspection server. Many resource summaries are justified, but the surface could be consolidated (e.g. pod-specific events and generalized events, or separate job/cronjob log helpers).

    Completeness3/5

    Core workload inspection is well covered: pods, containers, logs, events, deployments, replica sets, stateful sets, daemon sets, jobs, cronjobs, services, configmaps, PVCs, nodes, and namespaces. Notable gaps remain for common Kubernetes resources such as ingresses, endpoints, secrets, storage classes, persistent volumes, HPA, and RBAC objects.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources