Claude Kubernetes MCP Server
LocalAbout Claude Kubernetes MCP Server
A Go REST API that combines Kubernetes cluster context with Claude to answer questions about resources, namespaces, and GitLab merge requests. It is read-only and explicitly does not implement MCP's JSON-RPC transport, so MCP clients cannot connect directly.
Key features
- 01Read Kubernetes resources and events
- 02Map namespace resources, relationships, and health
- 03List warning events and failing CronJobs
- 04Ask Claude about cluster or GitLab context
- 05Authenticate with an API key or Workload Identity Federation
- 06Monitor ArgoCD access
Use cases
- 01Inspect resources and health in a namespace
- 02Find warning events and failed CronJobs
- 03Ask Claude about a Kubernetes resource
- 04Review a GitLab merge request with cluster context
MCP support
Despite its name, this is a REST API and does not implement the MCP JSON-RPC transport. MCP clients cannot connect directly; it is called over HTTP.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEClaude Kubernetes MCP Server
A Go server that answers questions about a Kubernetes cluster with Claude, using context from the Kubernetes API and, optionally, ArgoCD and GitLab.
Documentation: docs.blankcut.com/kubernetes-mcp-server — quick start, installation, every config key and endpoint, and troubleshooting.
What it does
- Reads the cluster — namespaces, any resource type (custom resources too), events, and a per-namespace map of resources, relationships and health.
- Finds problems without Claude — Warning events and failing CronJobs (with the end of the
failed run's log) become a list of issues in seconds (
?narrative=false). - Asks Claude about a resource, a whole namespace, or a GitLab merge request, with the context it collected.
- Watches its own ArgoCD access — it checks every 60 seconds that its token can still read Applications, so a lost RBAC grant shows up as an error rather than an empty list.
- Authenticates to Claude with an API key or Workload Identity Federation, so it can run without a long-lived key.
It only reads: nothing it does changes Kubernetes, ArgoCD or GitLab.
It is a REST API. Despite the name it does not implement the Model Context Protocol's JSON-RPC transport, so MCP clients such as Claude Desktop can't connect to it directly; call it over HTTP.
Quick start
Download a release binary (Linux and macOS, amd64 and arm64) from
Releases, write a config.yaml:
server:
address: ":8080"
writeTimeout: 300
auth:
apiKey: "${API_KEY}"
kubernetes:
inCluster: false # uses $KUBECONFIG or ~/.kube/config
claude:
apiKey: "${CLAUDE_API_KEY}"
baseURL: "https://api.anthropic.com"
modelID: "claude-sonnet-5"
maxTokens: 8192
and run it:
export API_KEY=$(openssl rand -hex 32) CLAUDE_API_KEY=sk-ant-...
./mcp-server-darwin-arm64 --config config.yaml
curl -s -H "X-API-Key: $API_KEY" \
"http://localhost:8080/api/v1/namespaces/default/analysis?narrative=false"
The quick start walks through it, including checksum verification.
Install
| Method | |
|---|---|
| Helm | helm install kubernetes-mcp-server ./helm/kubernetes-mcp-server --set secrets.apiKey=... --set secrets.claudeApiKey=... from a checkout of a release tag. See Installation. |
| Docker | blankcut/kubernetes-mcp-server (linux/amd64, linux/arm64); mount a config at /app/config.yaml. |
| Binary | Releases, with checksums.txt. |
| Source | Go 1.26+: cd kubernetes-claude-mcp && go build -o mcp-server ./cmd/server. |
Development
cd kubernetes-claude-mcp
go test ./...
go run ./cmd/server --config config.yaml --log-level debug
A Postman collection is in postman/. Changes are listed in
CHANGELOG.md; contributions are welcome — see CONTRIBUTING.md.
Donation
Please contribute to our coffee fund to help us continue to do great things: Buy Me Coffee
License
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.