Undeclared developer
Kubernetes MCP Server
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.
Snapshot
First seen
Apr 16, 2026
Claude metadata view
Discovery scoring is not shown for Claude connectors yet.
Dashboard
A cleaner view of the connector metadata: what it promises, what it exposes, and whether the profile is specific enough to trust.
Example prompts
0
Declared skills
0
Last seen
Apr 24, 2026
Connector summary
Capabilities
None declared
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.
What to tighten
Add more prompt-led screenshots or examples so the value proposition is legible at a glance.
Declare the developer clearly. Missing ownership weakens trust and profile completeness.
Add a canonical website or docs link. External trust signals are still thin.
Actions
The highest-leverage fixes based on the current metadata snapshot.
Recommendation 1
Add more prompt-led screenshots or examples so the value proposition is legible at a glance.
Recommendation 2
Declare the developer clearly. Missing ownership weakens trust and profile completeness.
Recommendation 3
Add a canonical website or docs link. External trust signals are still thin.