Kubernetes MCP Server
MCP server for interacting with Kubernetes clusters via kubectl
- Category
- Pending
- Primary Subcategory
- Cloud Infrastructure Management
Integration details
Description
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.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Cloud Infrastructure Management
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Unknown
- First tracked
- 2026-08-11
- Tool count
- 22
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Kubernetes MCP Server isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What the current score measures

Remote Connectors Claude can surface from the Connector picker.
About Claude's Discoverability Score
Your Connector now competes to appear for users’ prompts
22 tools agents can invoke
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.
