MCP Server Kubernetes
MCP Server that can connect to a Kubernetes cluster and manage it.
<a href="https://glama.ai/mcp/servers/w71ieamqrt"><img width="380" height="200" src="https://glama.ai/mcp/servers/w71ieamqrt/badge" /></a>
Usage with Claude Desktop
The server will automatically connect to your current kubectl context. Make sure you have:
- kubectl installed and in your PATH
- A valid kubeconfig file with contexts configured
- Access to a Kubernetes cluster configured for kubectl (e.g. minikube, Rancher Desktop, GKE, etc.)
- Helm v3 installed and in your PATH (no Tiller required). Optional if you don't plan to use Helm.
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.Usage with mcp-chat
mcp-chat is a CLI chat client for MCP servers. You can use it to interact with the Kubernetes server.
Alternatively, pass it your existing Claude Desktop configuration file from above (Linux should pass the correct path to config):
Mac:
Windows:
Features
- Connect to a Kubernetes cluster
- List all pods, services, deployments
- List, Describe nodes
- Create, describe, delete a pod
- List all namespaces, create a namespace
- Create custom pod & deployment configs, update deployment replicas
- Create, describe, delete, update a service
- Create, get, update, delete a ConfigMap
- Get logs from a pod for debugging (supports pods, deployments, jobs, and label selectors)
- Support Helm v3 for installing charts
- kubectl explain and kubectl api-resources support
- Get Kubernetes events from the cluster
- Port forward to a pod or service
- Create, list, and decribe cronjobs
- Non-destructive mode for read and create/update-only access to clusters
Local Development
Make sure that you have bun installed. Clone the repo & install dependencies:
Development Workflow
- Start the server in development mode (watches for file changes):
- Run unit tests:
- Build the project:
- Local Testing with Inspector
- Local testing with Claude Desktop
- Local testing with mcp-chat
Contributing
See the CONTRIBUTING.md file for details.
Advanced
Additional Advanced Features
For more advanced information like using SSE transport, Non-destructive mode with
ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS, see the ADVANCED_README.md.Architecture
This section describes the high-level architecture of the MCP Kubernetes server.
Request Flow
The sequence diagram below illustrates how requests flow through the system:
Publishing new release
Go to the releases page, click on "Draft New Release", click "Choose a tag" and create a new tag by typing out a new version number using "v{major}.{minor}.{patch}" semver format. Then, write a release title "Release v{major}.{minor}.{patch}" and description / changelog if necessary and click "Publish Release".
This will create a new tag which will trigger a new release build via the cd.yml workflow. Once successful, the new release will be published to npm. Note that there is no need to update the package.json version manually, as the workflow will automatically update the version number in the package.json file & push a commit to main.
Not planned
Authentication / adding clusters to kubectx.
MCP Server Kubernetes
MCP Server that can connect to a Kubernetes cluster and manage it.
<a href="https://glama.ai/mcp/servers/w71ieamqrt"><img width="380" height="200" src="https://glama.ai/mcp/servers/w71ieamqrt/badge" /></a>
Usage with Claude Desktop
The server will automatically connect to your current kubectl context. Make sure you have:
- kubectl installed and in your PATH
- A valid kubeconfig file with contexts configured
- Access to a Kubernetes cluster configured for kubectl (e.g. minikube, Rancher Desktop, GKE, etc.)
- Helm v3 installed and in your PATH (no Tiller required). Optional if you don't plan to use Helm.
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.Usage with mcp-chat
mcp-chat is a CLI chat client for MCP servers. You can use it to interact with the Kubernetes server.
Alternatively, pass it your existing Claude Desktop configuration file from above (Linux should pass the correct path to config):
Mac:
Windows:
Features
- Connect to a Kubernetes cluster
- List all pods, services, deployments
- List, Describe nodes
- Create, describe, delete a pod
- List all namespaces, create a namespace
- Create custom pod & deployment configs, update deployment replicas
- Create, describe, delete, update a service
- Create, get, update, delete a ConfigMap
- Get logs from a pod for debugging (supports pods, deployments, jobs, and label selectors)
- Support Helm v3 for installing charts
- kubectl explain and kubectl api-resources support
- Get Kubernetes events from the cluster
- Port forward to a pod or service
- Create, list, and decribe cronjobs
- Non-destructive mode for read and create/update-only access to clusters
Local Development
Make sure that you have bun installed. Clone the repo & install dependencies:
Development Workflow
- Start the server in development mode (watches for file changes):
- Run unit tests:
- Build the project:
- Local Testing with Inspector
- Local testing with Claude Desktop
- Local testing with mcp-chat
Contributing
See the CONTRIBUTING.md file for details.
Advanced
Additional Advanced Features
For more advanced information like using SSE transport, Non-destructive mode with
ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS, see the ADVANCED_README.md.Architecture
This section describes the high-level architecture of the MCP Kubernetes server.
Request Flow
The sequence diagram below illustrates how requests flow through the system:
Publishing new release
Go to the releases page, click on "Draft New Release", click "Choose a tag" and create a new tag by typing out a new version number using "v{major}.{minor}.{patch}" semver format. Then, write a release title "Release v{major}.{minor}.{patch}" and description / changelog if necessary and click "Publish Release".
This will create a new tag which will trigger a new release build via the cd.yml workflow. Once successful, the new release will be published to npm. Note that there is no need to update the package.json version manually, as the workflow will automatically update the version number in the package.json file & push a commit to main.
Not planned
Authentication / adding clusters to kubectx.