Assess and monitor the risk of the Kubernetes MCP Server connector in Anthropic Claude, OpenAI Codex, and Microsoft Copilot.
MCP server for interacting with Kubernetes clusters via kubectl
Viewing Details For
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 - [x] Connect to a Kubernetes cluster - [x] 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.
Tools the Kubernetes MCP Server Connector Exposes to Anthropic Claude
PromptArmor tracks connector risk across Claude, Codex, Copilot, and other MCP-enabled platforms. Book a demo to see the live connector risk dashboard for your environment.
Book a demo