A
licenseB
qualityD
maintenanceEnables 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.
11
10,522 npm
MIT
mcp-server-kubernetes
by ACRT-EVAL
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,522 npmMIT
- AlicenseBqualityDmaintenanceEnables connecting to a Kubernetes cluster through kubectl context to list and manage pods, services, deployments, nodes, and namespaces, create or delete pods, describe pods, and retrieve logs for debugging.1110,522 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,522 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,522 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,522 npmMIT
TDQS
B3/5.0
Scored across 11 tools
Disambiguation4/5
Most tools target distinct resource/action pairs, and names like list_pods vs create_pod vs describe_pod are easy to distinguish. The only mild overlap is between describe_pod and get_logs, but their descriptions clarify the difference (status/containers vs logs).
Naming Consistency4/5
The set mostly follows a clear verb_noun convention: list_pods, create_deployment, delete_pod, describe_pod, get_logs. The lone outlier is cleanup, which lacks a resource noun and breaks the pattern slightly.
Tool Count5/5
With 11 tools, the server is well within the ideal 3–15 range for a scoped Kubernetes operations surface. Each tool maps to a recognizable kubectl-style operation without feeling bloated.
Completeness3/5
The surface covers listing several core resource types plus create/delete/describe for pods and create for deployments, but lifecycle coverage is uneven. There is no delete_deployment, no update/scale operation, no create_service, and no exec or configmap/secret handling, so agents will hit dead ends for common workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues