Loading...
This MCP server enables interaction with Kubernetes clusters, offering both read and write operations, including resource management, diagnostics, and Helm chart deployment.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
This MCP server enables interaction with Kubernetes clusters, offering both read and write operations, including resource management, diagnostics, and Helm chart deployment.
This server provides powerful Kubernetes management capabilities, but its safety depends heavily on configuration and usage. Running in non-destructive mode significantly reduces risk. Exercise caution with kubectl_generic and untrusted Helm charts.
Performance depends on the size and complexity of the Kubernetes cluster. Large clusters may experience slower response times.
Cost is primarily associated with the resources consumed by the Kubernetes cluster itself. The MCP server has minimal overhead.
npx mcp-chat --server "npx mcp-server-kubernetes"{
"mcpServers": {
"kubernetes": {
"command": "npx",
"args": ["mcp-server-kubernetes"]
}
}
}ALLOW_ONLY_NON_DESTRUCTIVE_TOOLSkubectl_getRetrieves Kubernetes resources.
Read-only operation.
kubectl_describeDescribes Kubernetes resources.
Read-only operation.
kubectl_createCreates Kubernetes resources.
Creates new resources, but doesn't modify existing ones without further action.
kubectl_applyApplies YAML manifests to create or update resources.
Can modify existing resources based on the manifest.
kubectl_deleteDeletes Kubernetes resources.
Destructive operation that permanently removes resources.
kubectl_logsRetrieves logs from Kubernetes pods.
Read-only operation.
kubectl_scaleScales the number of replicas in a deployment or replicaset.
Modifies the number of replicas, potentially impacting application availability.
kubectl_patchUpdates specific fields of a Kubernetes resource.
Can modify resource configurations, potentially causing unexpected behavior.
kubectl_rolloutManages deployment rollouts (status, history, pause, resume, undo).
Can alter the state of deployments, potentially disrupting service.
kubectl_genericExecutes arbitrary kubectl commands.
Unrestricted access to kubectl functionality, including destructive operations.
helm_template_applyApplies a Helm chart template to the cluster.
Can create or modify resources based on the template.
helm_template_uninstallUninstalls a Helm chart template from the cluster.
Removes resources deployed by the Helm chart.
cleanup_podsCleans up problematic pods in various error states.
Deletes pods, potentially disrupting workloads.
node_managementCordons, drains, and uncordons Kubernetes nodes.
Can disrupt workloads running on the affected nodes.
k8s-diagnoseGuides through a systematic Kubernetes troubleshooting flow for pods.
Primarily read-only, guiding the user through diagnostic steps.
Token
hybrid
This server provides powerful Kubernetes management capabilities, but its safety depends heavily on configuration and usage. Running in non-destructive mode significantly reduces risk. Exercise caution with `kubectl_generic` and untrusted Helm charts.
Autonomy is determined by the permissions granted to the kubeconfig used by the server. Exercise caution when granting broad permissions.
Production Tip
Run the server in non-destructive mode in production environments to prevent accidental data loss.
The server loads kubeconfig from `~/.kube/config` by default. See ADVANCED_README.md for other options.
Non-destructive mode disables all destructive operations. Enable it by setting the environment variable `ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS=true`.
The server automatically masks secrets in `kubectl get secrets` commands. This does not affect logs.
Yes, by configuring multiple contexts in your kubeconfig file and switching between them using the `kubectl_context` tool.
Yes, Helm v3 is supported. Helm v2 (Tiller) is not supported.
Check the server's standard output for error messages. Ensure that kubectl is installed and configured correctly.
The required permissions depend on the operations you intend to perform. Read-only operations require minimal permissions, while destructive operations require broader access.