Kubernetes Read-Only MCP
Related Servers
Alternatives to Kubernetes Read-Only MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables operators and MCP clients to perform read-only, multi-cluster Kubernetes diagnostics by correlating deployment inventory, approved Prometheus metrics, firing alerts, and reusable troubleshooting skills without executing cluster commands or modifying workloads. It exposes tools, resources, and prompts for deployment health checks, metric queries, alert inspection, and skill discovery.MIT
- AlicenseBqualityCmaintenanceEnables 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.57Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- FlicenseNot gradedqualityCmaintenanceEnables read-only interaction with a Kubernetes cluster, allowing listing of nodes, pods, deployments, and services, as well as fetching pod logs.-
- AlicenseNot gradedqualityBmaintenanceEnables 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
TDQS
Scored across 18 tools
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.
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.
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.
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.