Skip to main content
Glama
jhmorimoto

Kubernetes Read-Only MCP

by jhmorimoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Kubernetes Read-Only MCP

No user-submitted related servers found.

    Related Servers

    • kube-diagnostics-mcp

      ranson21
      A
      license
      B
      quality
      C
      maintenance
      Enables read-only, stack-aware diagnostics for microservices on Kubernetes, turning debugging runbooks into conversational tools that investigate slow requests, changes, leaks, and in-pod conditions without exposing cluster credentials.
      57
      Apache 2.0

    • k8s-troubleshoot-mcp

      NanaGyamfiPrempeh30
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to diagnose Kubernetes clusters through read-only MCP tools, such as inspecting pod status, logs, events, nodes, deployments, and HPA metrics via natural language queries.
      MIT

    • Kubernetes MCP Server

      vivekbala
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables real-time Kubernetes cluster observability and debugging through standardized MCP interface. Provides access to pods, services, nodes, events, and includes built-in tools for cluster health analysis and issue identification.
      -

    • k8s-mcp-server

      gaelsg
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only interaction with a Kubernetes cluster, allowing listing of nodes, pods, deployments, and services, as well as fetching pod logs.
      -

    • k8s-ops-mcp

      eliffkeskin
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only Kubernetes cluster diagnostics through MCP tools, allowing a local LLM to inspect pods and events and debug issues via natural language queries.
      MIT

    • K8s Doctor MCP

      ongjin
      A
      license
      B
      quality
      D
      maintenance
      AI-powered Kubernetes diagnostics that analyzes pod crashes, logs, and cluster health to provide root cause analysis and actionable solutions for common issues like CrashLoopBackOff, OOM kills, and connection errors.
      8
      9 npm
      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

    A3.5/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target clearly distinct resource areas, but list_api_resources, list_crds, and list_resources have similar names and overlapping discovery/list purposes. Generic list/get tools also overlap with specialized listers, though descriptions clarify their intended use.

    Naming Consistency5/5

    All tools consistently use lowercase snake_case verb_noun naming: list_* for collections, get_* for single objects and logs, and describe_pod for detailed pod status. No mixed conventions or unpredictable patterns.

    Tool Count4/5

    18 tools is slightly above the typical 3-15 well-scoped range, but the breadth of Kubernetes read-only scenarios justifies the count. Each tool addresses a meaningful area and the overlap is modest.

    Completeness4/5

    The surface covers cluster health, discovery, common workloads, events, storage, RBAC, and secrets, with generic list_resources/get_resource filling gaps for resource types without dedicated tools. Missing convenience getters for services, ingresses, and jobs, but no dead ends exist.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources