Kubernetes

MCP Server Kubernetes

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

https://github.com/user-attachments/assets/f25f8f4e-4d04-479b-9ae0-5dac452dd2ed

Usage with Claude Desktop

1{
2  "mcpServers": {
3    "kubernetes": {
4      "command": "npx",
5      "args": ["mcp-server-kubernetes"]
6    }
7  }
8}

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.

1npx mcp-chat --server "npx mcp-server-kubernetes"

Alternatively, pass it your existing Claude Desktop configuration file from above (Linux should pass the correct path to config):

Mac:

1npx mcp-chat --config "~/Library/Application Support/Claude/claude_desktop_config.json"

Windows:

1npx mcp-chat --config "%APPDATA%\Claude\claude_desktop_config.json"

Features

[x] Connect to a Kubernetes cluster
[x] List all pods, services, deployments, nodes
[x] Create, describe, delete a pod
[x] List all namespaces, create a namespace
[x] Create custom pod & deployment configs, update deployment replicas
[x] Get logs from a pod for debugging (supports pods, deployments, jobs, and label selectors)
[x] Support Helm v3 for installing charts
- Install charts with custom values
- Uninstall releases
- Upgrade existing releases
- Support for namespaces
- Support for version specification
- Support for custom repositories
[x] kubectl explain and kubectl api-resources support
[x] Get Kubernetes events from the cluster
[x] Port forward to a pod or service
[x] Create, list, and decribe cronjobs

Local Development

1git clone https://github.com/Flux159/mcp-server-kubernetes.git
2cd mcp-server-kubernetes
3bun install

Development Workflow

Start the server in development mode (watches for file changes):

1bun run dev

Run unit tests:

1bun run test

Build the project:

1bun run build

Local Testing with Inspector

1npx @modelcontextprotocol/inspector node dist/index.js
2# Follow further instructions on terminal for Inspector link

Local testing with Claude Desktop

1{
2  "mcpServers": {
3    "mcp-server-kubernetes": {
4      "command": "node",
5      "args": ["/path/to/your/mcp-server-kubernetes/dist/index.js"]
6    }
7  }
8}

Local testing with mcp-chat

1npm run chat

Contributing

See the CONTRIBUTING.md file for details.

Advanced

For more advanced information like using SSE transport, 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:

1sequenceDiagram
2    participant Client
3    participant Transport as StdioTransport
4    participant Server as MCP Server
5    participant Handler as Request Handler
6    participant K8sManager as KubernetesManager
7    participant K8s as Kubernetes API
8
9    Client->>Transport: Send Request via STDIO
10    Transport->>Server: Forward Request
11
12    alt Tools Request
13        Server->>Handler: Route to tools handler
14        Handler->>K8sManager: Execute tool operation
15        K8sManager->>K8s: Make API call
16        K8s-->>K8sManager: Return result
17        K8sManager-->>Handler: Process response
18        Handler-->>Server: Return tool result
19    else Resource Request
20        Server->>Handler: Route to resource handler
21        Handler->>K8sManager: Get resource data
22        K8sManager->>K8s: Query API
23        K8s-->>K8sManager: Return data
24        K8sManager-->>Handler: Format response
25        Handler-->>Server: Return resource data
26    end
27
28    Server-->>Transport: Send Response
29    Transport-->>Client: Return Final Response

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.

Contents