mcp-server-kubernetes
Related Servers
Alternatives to mcp-server-kubernetes
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables connecting to a Kubernetes cluster to manage it, including listing pods, services, deployments, nodes, and namespaces, creating and deleting pods, describing pods, and retrieving logs for debugging.10,601 npmMIT
- AlicenseBqualityDmaintenanceEnables connection to a Kubernetes cluster to list and manage pods, services, deployments, nodes, and namespaces, including creating, deleting, describing pods and retrieving logs for debugging.1110,601 npmMIT
- AlicenseBqualityDmaintenanceEnables connection to a Kubernetes cluster to list and manage pods, services, deployments, and nodes, create/delete/describe pods, inspect namespaces, and retrieve logs for debugging.1110,601 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects to a Kubernetes cluster through the current kubectl context and enables listing, creating, deleting, and describing pods, services, deployments, nodes, and namespaces, plus retrieving logs for debugging.10,601 npmMIT
- AlicenseBqualityDmaintenanceConnects to a Kubernetes cluster using your current kubectl context, letting an assistant list pods, services, deployments, nodes, and namespaces, create, delete, and describe pods, and pull logs for debugging. It turns everyday cluster management into natural-language tool calls.1110,601 npmMIT
- AlicenseCqualityDmaintenanceEnables connecting to a Kubernetes cluster to manage resources and troubleshoot workloads with kubectl and Helm operations, including logs, scaling, port forwarding, and non-destructive mode.2210,601 npmMIT
TDQS
Scored across 11 tools
Most tools target clearly distinct Kubernetes resources and actions, such as list_pods vs list_deployments vs create_pod. The only mild ambiguity is cleanup, which could overlap conceptually with delete_pod if 'managed resources' includes pods created by the server.
The set mostly follows a predictable verb_noun pattern: list_pods, create_pod, delete_pod, describe_pod, get_logs. cleanup is the main deviation because it uses a single vague verb without a resource noun.
With 11 tools, the server is well-scoped for common Kubernetes inspection and basic pod/deployment operations. Each tool has a reasonably clear place and the count is neither thin nor bloated.
The surface covers listing core resources, creating pods/deployments, deleting pods, describing pods, logs, and cleanup. However, it lacks obvious lifecycle operations such as deleting deployments/services, updating or scaling deployments, and describing deployments/services, which limits common Kubernetes workflows.