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
11,892 npm
MIT
MCP Server Kubernetes
by yasir27uk
Related Servers
Alternatives to MCP Server Kubernetes
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive Kubernetes cluster management through kubectl operations, Helm chart deployments, pod troubleshooting, and node management. Supports both read-only and full cluster administration capabilities with built-in safety features.11,892 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.1111,892 npmMIT
- AlicenseBqualityDmaintenanceEnables 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.1111,892 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.1111,892 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables comprehensive Kubernetes cluster management through kubectl operations and Helm chart management. Supports resource operations, logging, scaling, rollouts, and diagnostics with multiple transport modes and security features.-
TDQS
C2.9/5.0
Scored across 22 tools
Disambiguation3/5
Most tools target distinct Kubernetes verbs or resources, but kubectl_create, kubectl_apply, and kubectl_patch overlap in resource creation/update, and kubectl_generic acts as a catch-all that duplicates every other kubectl tool. cleanup is also vaguely scoped relative to delete and uninstall operations.
Naming Consistency3/5
Core tools use a consistent kubectl_ prefix with snake_case, but the set mixes prefixes (helm_* and no prefix), patterns like verb_noun (install_helm_chart), noun phrases (node_management), and bare verbs (cleanup, ping). Readable but not predictable across the whole set.
Tool Count4/5
22 tools is on the heavy side but each covers a meaningful Kubernetes or Helm operation across resource lifecycle, node management, port forwarding, and exec. The existence of kubectl_generic makes some dedicated tools redundant, yet the count remains reasonable for the domain's breadth.
Completeness4/5
The surface covers core resource lifecycle (get, describe, create, apply, delete, patch, scale, rollout), Helm install/upgrade/uninstall, node management, port forwarding, exec, and context, with kubectl_generic as a fallback. Minor gaps like Helm list/rollback exist, but agents can work around most with generic commands.