Kubernetes MCP Server listing history

MCP Server that can connect to a Kubernetes cluster and manage it.

By default, the server loads kubeconfig from ~/.kube/config.

The server will automatically connect to your current kubectl context. Make sure you have:

1. kubectl installed and in your PATH
2. A valid kubeconfig file with contexts configured
3. Access to a Kubernetes cluster configured for kubectl (e.g. minikube, Rancher Desktop, GKE, etc.)
4. Optional: Helm v3 installed and in your PATH.

You can verify your connection by asking Claude to list your pods or create a test deployment.

If you have errors open up a standard terminal and run kubectl get pods to see if you can connect to your cluster without credentials issues.

Features

• Connect to a Kubernetes cluster
• Unified kubectl API for managing resources
• Get or list resources with kubectl_get
• Describe resources with kubectl_describe
• List resources with kubectl_get
• Create resources with kubectl_create
• Apply YAML manifests with kubectl_apply
• Delete resources with kubectl_delete
• Get logs with kubectl_logs
• and more.