K8s read-only MCP server
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Topics declared
claude mcp add mcp-k8s-ro -- docker run -i --rm /home/nonroot/.kube{
"mcpServers": {
"mcp-k8s-ro": {
"command": "docker",
"args": ["run", "-i", "--rm", "/home/nonroot/.kube"]
}
}
}Resumen de MCP Servers
[](https://github.com/your-ko/mcp-k8s-ro/actions/workflows/main.yaml)
[](https://github.com/your-ko/mcp-k8s-ro/actions/workflows/golangci-lint.yaml)
[](https://github.com/your-ko/mcp-k8s-ro/actions/workflows/link-validator.yaml)
# mcp-k8s-ro
A read-only MCP server that gives Claude access to Kubernetes clusters. Built in Go, it communicates over stdio using the MCP protocol.
## Design
- **Read-only** — only `get`, `describe`, `logs`, and `top` style operations. No create, update, or delete. If a mutating operation is needed, the server prints the equivalent `kubectl` command for you to run manually. Safe to use while on-call at night: Claude can never accidentally mutate your cluster, even under prompt fatigue.
- **Secret-safe** — secret values are masked before being sent to the model, so your secrets cannot leak due to misconfiguration or prompt injection.
- **Token-efficient** — responses include only relevant fields (name, status, restarts, etc.) rather than raw Kubernetes API objects, keeping context usage low.
- **Cluster-aware** — every response includes the active context and cluster name, so Claude always knows which cluster it is talking to.
- **Context-pinned** — the server locks to the active kubeconfig context at startup. Switching contexts in another terminal has no effect on the running server.
- **No extra infra** — runs as a local binary or Docker container, connects to whatever kubeconfig context is active at startup.
## Redacted fields
| Object/Field | Reason |
|--------------------------------------------------------|----------------------------------------------------------|
| Secret.data | Secret leak prevention |
| Secret.stringData | Secret leak prevention |
| CertificateSigningRequest.spec.request | Large base64 PEM blob, no diagnostic value, saves tokens |
| Certificate (cert-manager) .spec.keystores | Cert chain PEM blobs, no diagnostic value, saves tokens |
| Certificate (cert-manager) status.conditions[].message | Cert chain PEM blobs, no diagnostic value, saves tokens |
| *.managedFields | No diagnostic value, saves tokens |
## Tools
| Tool | Description |
|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `k8s_list_resources` | List any resource type by name — pods, deployments, CRDs, etc. Accepts optional namespace filter. Returns name, status, readiness, restarts, node, IP, and more depending on resource kind. |
| `k8s_describe_resource` | Return the full YAML of a single resource. Secret data is masked. |
| `k8s_list_resource_types` | List all available resource types via the discovery API. Accepts optional API group filter. |
| `k8s_get_logs` | Fetch pod logs. Supports container selector, tail lines, and `--previous` for crashed containers. |
| `k8s_get_events` | List Kubernetes events for a namespace or the whole cluster, sorted by most recent. |
| `k8s_top_pods` | CPU and memory usage per pod, with per-container breakdown. Requires metrics-server. |
| `k8s_top_nodes` | CPU and memory usage per node, with percentage of allocatable capacity. Requires metrics-server. |
## Configuration
| Environment variable | Default | Description |
|----------------------|------------------|-------------------------|
| `KUBECONFIG` | `~/.kube/config` | Path to kubeconfig file |
## Usage with Claude
### Docker (recommended)
```bash
claude mcp add --scope user --transport stdio k8s-ro \
-- docker run --rm -i -v ~/.kube:/home/nonroot/.kube:ro ghcr.io/your-ko/mcp-k8s-ro:latest
```
Pinning a specific version (check the [latest release](https://github.com/your-ko/mcp-k8s-ro/releases/latest) ) is recommended for production use:
```bash
claude mcp add --scope user --transport stdio k8s-ro \
-- docker run --rm -i -v ~/.kube:/home/nonroot/.kube:ro ghcr.io/your-ko/mcp-k8s-ro:1.1.0
```
### Binary
Download a pre-built binary from [GitHub Releases](https://github.com/your-ko/mcp-k8s-ro/releases):
```bash
# macOS Apple Silicon — change ARCH for other platforms: darwin-amd64, linux-amd64, linux-arm64
ARCH=darwin-arm64
VERSION=$(curl -fsSL https://api.github.com/repos/your-ko/mcp-k8s-ro/releases/latest | grep tag_name | cut -d'"' -f4)
curl -fsSL "https://github.com/your-ko/mcp-k8s-ro/releases/download/${VERSION}/mcp-k8s-ro-${VERSION}-${ARCH}" -o ~/.local/bin/mcp-k8s-ro
chmod +x ~/.local/bin/mcp-k8s-ro
xattr -d com.apple.quarantine ~/.local/bin/mcp-k8s-ro 2>/dev/null # macOS only: remove Gatekeeper quarantine
claude mcp add --scope user --transport stdio k8s-ro ~/.local/bin/mcp-k8s-ro
```
> **macOS Gatekeeper**: The binary is not code-signed, so macOS will block it.
> The `xattr` command above removes the quarantine flag. Alternatively, go to System Settings → Privacy & Security and click "Allow Anyway" after the first blocked attempt.

Or build from source:
```bash
make build
claude mcp add --scope user --transport stdio k8s-ro ./bin/mcp-k8s-ro
```
### Custom kubeconfig location
If your kubeconfig is not at `~/.kube/config`, set the `KUBECONFIG` environment variable:
```bash
# Binary
claude mcp add --scope user --transport stdio -e KUBECONFIG=/path/to/kubeconfig k8s-ro ~/.local/bin/mcp-k8s-ro
# Docker
claude mcp add --scope user --transport stdio k8s-ro \
-- docker run --rm -i -e KUBECONFIG=/config/kubeconfig -v /path/to/kubeconfig:/config/kubeconfig:ro ghcr.io/your-ko/mcp-k8s-ro:latest
```
## Single-cluster design
The server intentionally operates on one kubeconfig context and provides no tool to switch clusters at runtime. The reasons are:
- **Prompt injection isolation** — a malicious value in one cluster's resources (e.g. a pod annotation) cannot instruct Claude to pivot to a different cluster, including production.
- **Explicit audit boundary** — every tool response includes the context and cluster name, so there is never ambiguity about which cluster was queried.
**To point the server at a different cluster**, stop the server, switch context, and restart:
```bash
kubectl config use-context my-other-cluster
# then restart the MCP server / reload Claude Desktop
```
**To work with multiple clusters simultaneously**, register a separate server instance per cluster in your MCP config:
```json
{
"mcpServers": {
"k8s-staging": {
"type": "stdio",
"command": "/path/to/bin/mcp-k8s-ro",
"env": { "KUBECONFIG": "/path/to/.kube/config" }
},
"k8s-prod": {
"type": "stdio",
"command": "/path/to/bin/mcp-k8s-ro",
"env": { "KUBECONFIG": "/path/to/.kube/config-prod" }
}
}
}
```
Claude will address each server by name and each instance only ever sees its own cluster.
## MCP registry
This server is published on [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/?q=mcp-k8s-ro)
Lo que la gente pregunta sobre mcp-k8s-ro
¿Qué es your-ko/mcp-k8s-ro?
+
your-ko/mcp-k8s-ro es mcp servers para el ecosistema de Claude AI. K8s read-only MCP server Tiene 1 estrellas en GitHub y se actualizó por última vez today.
¿Cómo se instala mcp-k8s-ro?
+
Puedes instalar mcp-k8s-ro clonando el repositorio (https://github.com/your-ko/mcp-k8s-ro) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar your-ko/mcp-k8s-ro?
+
Nuestro agente de seguridad ha analizado your-ko/mcp-k8s-ro y le ha asignado un Trust Score de 82/100 (tier: Trusted). Revisa el desglose completo de comprobaciones superadas y flags en esta página.
¿Quién mantiene your-ko/mcp-k8s-ro?
+
your-ko/mcp-k8s-ro es mantenido por your-ko. La última actividad registrada en GitHub es de today, con 4 issues abiertos.
¿Hay alternativas a mcp-k8s-ro?
+
Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.
Despliega mcp-k8s-ro en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/your-ko-mcp-k8s-ro)<a href="https://claudewave.com/repo/your-ko-mcp-k8s-ro"><img src="https://claudewave.com/api/badge/your-ko-mcp-k8s-ro" alt="Featured on ClaudeWave: your-ko/mcp-k8s-ro" width="320" height="64" /></a>Más MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
The fastest path to AI-powered full stack observability, even for lean teams.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!