All servers / Infrastructure / Kubernetes
Kubernetes
MCP server for interacting with Kubernetes clusters via kubectl
Tested by ConnectATDScore 91 out of 100. Tested 2026-11-17 on package version 4.2.3. Package: mcp-server-kubernetes · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 17 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (106.4 seconds including download)
- Tools offered: 23
- Last published: 2026-11-13
- Weekly downloads (npm): 27,037
- License: MIT · Direct dependencies: 12
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
cleanupno parametersCleanup all managed resources
kubectl_get9 of 9 parameters describedGet or list Kubernetes resources by resource type, name, and optionally namespace
kubectl_describe5 of 5 parameters describedDescribe Kubernetes resources by resource type, name, and optionally namespace
kubectl_apply6 of 6 parameters describedApply a Kubernetes YAML manifest from a string or file
kubectl_delete10 of 10 parameters describedDelete Kubernetes resources by resource type, name, labels, or from a manifest file
kubectl_create23 of 23 parameters describedCreate Kubernetes resources using various methods (from file or using subcommands)
kubectl_logs12 of 12 parameters describedGet logs from Kubernetes resources like pods, deployments, or jobs
kubectl_scale5 of 5 parameters describedScale a Kubernetes deployment
kubectl_patch8 of 8 parameters describedUpdate field(s) of a resource using strategic merge patch, JSON merge patch, or JSON patch
kubectl_rollout9 of 9 parameters describedManage the rollout of a resource (e.g., deployment, daemonset, statefulset)
kubectl_context5 of 5 parameters describedManage Kubernetes contexts - list, get, or set the current context
kubectl_reconnectno parametersReconnect to the Kubernetes API server by recreating all API clients. Use this after cluster upgrades (e.g., EKS control plane upgrades that rotate ENIs/IPs) to force fresh DNS resolution and new TCP connections.
explain_resource5 of 5 parameters describedGet documentation for a Kubernetes resource or field
install_helm_chart9 of 9 parameters describedInstall a Helm chart with support for both standard and template-based installation
upgrade_helm_chart7 of 7 parameters describedUpgrade an existing Helm chart release
uninstall_helm_chart3 of 3 parameters describedUninstall a Helm chart release
node_management9 of 9 parameters describedManage Kubernetes nodes with cordon, drain, and uncordon operations
port_forward0 of 5 parameters describedForward a local port to a port on a Kubernetes resource
stop_port_forward0 of 1 parameter describedStop a port-forward process
exec_in_pod6 of 6 parameters describedExecute a command in a Kubernetes pod or container and return the output. Command must be an array of strings where the first element is the executable and remaining elements are arguments. This executes directly without shell interpretation for security.
list_api_resources5 of 5 parameters describedList the API resources available in the cluster
kubectl_generic10 of 10 parameters describedExecute any kubectl command with the provided arguments and flags
pingno parametersVerify that the counterpart is still responsive and the connection is alive.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.