k8s-mcp-go
Safe, read-only-by-default Kubernetes access for AI agents.
A Kubernetes MCP server that lets AI assistants inspect your cluster safely — without giving them unrestricted kubectl.
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
mcpb https://github.com/kaneg/k8s-mcp-go/releases/download/v0.4.6/k8s-mcp-go_0.4.6_darwin_amd64.mcpbO Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add io.github.kaneg-k8s-mcp-go -- mcpb https://github.com/kaneg/k8s-mcp-go/releases/download/v0.4.6/k8s-mcp-go_0.4.6_darwin_amd64.mcpbExecute em um terminal.
{ "mcpServers": { "io.github.kaneg-k8s-mcp-go": { "command": "mcpb", "args": [ "https://github.com/kaneg/k8s-mcp-go/releases/download/v0.4.6/k8s-mcp-go_0.4.6_darwin_amd64.mcpb" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Safe, read-only-by-default Kubernetes access for AI agents.
A Kubernetes MCP server that lets AI assistants inspect your cluster safely — without giving them unrestricted kubectl.
Safe Kubernetes access for AI agents via MCP. Read-only by default, with explicit permission modes.
readonly, readwrite, or dangerous before the assistant starts.io.github.kaneg/k8s-mcp-go for MCP Registry consumers and packaged clients.io.github.kaneg/k8s-mcp-go.server.json.Most AI agents can use Kubernetes tools. The real problem is how to stop them from changing the wrong thing.
Giving an AI raw kubectl access is risky. Even a capable model can:
k8s-mcp-go gives AI agents a guardrailed interface to Kubernetes instead of unrestricted shell access.
It is built for the real-world question:
How can I let AI help with Kubernetes, without letting it break my cluster?
You choose the boundary up front:
readonly (default)For diagnosis, inspection, and safe exploration.
AI can do things like:
It cannot modify workloads or delete resources.
readwriteFor controlled operational workflows.
AI can do things like:
It still cannot perform the most destructive operations.
dangerousFull access.
Use this only when you explicitly want AI to be able to:
If you are unsure, use readonly.
Download the .mcpb bundle for your platform from Releases. MCPB-compatible clients (Claude Desktop, Cursor, etc.) can install it directly — no Docker, no Go, no manual setup.
Grab the binary archive from Releases and extract it:
# Example: Linux x86_64
tar xzf k8s-mcp-go_*_linux_amd64.tar.gz
chmod +x k8s-mcp-go
sudo mv k8s-mcp-go /usr/local/bin/
Then add it to your MCP client.
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"k8s": {
"command": "k8s-mcp-go",
"args": ["-mode=readonly"]
}
}
}
Cursor (.cursor/mcp.json):
{
"mcpServers": {
"k8s": {
"command": "k8s-mcp-go",
"args": ["-mode=readonly"]
}
}
}
Restart your client and start asking questions about your cluster.
Once installed, ask your AI assistant things like:
In readonly mode, the assistant can investigate but cannot change the cluster.
Because the problem is not whether AI can talk to Kubernetes. The problem is whether it can do so safely.
kubectl is powerful, but it does not give you a product-level permission mode for AI behavior.
With k8s-mcp-go, you decide whether the assistant can:
The permission boundary is the product.
Tools are grouped by permission level.
Names start with an action verb such as get, list, or delete; top_nodes
and top_pods retain Kubernetes' established kubectl top terminology.
Prefer the dedicated delete tools above when one exists. Use delete_resource
as the fallback for other kinds. It resolves namespaced versus cluster-scoped
resources through Kubernetes discovery.
{"api_version":"v1","kind":"ServiceAccount","namespace":"apps","name":"builder"}
{"api_version":"rbac.authorization.k8s.io/v1","kind":"ClusterRole","name":"auditor"}
Configuration is selected in this order:
KUBECONFIG, when set.~/.kube/config when running outside a cluster.An explicit KUBECONFIG is authoritative. If it cannot be loaded, the server
returns an error instead of silently switching to the Pod's ServiceAccount.
In-cluster configuration uses Kubernetes' mounted token file so projected
ServiceAccount token rotation continues to work without copying tokens into a
kubeconfig.
git clone https://github.com/kaneg/k8s-mcp-go.git
cd k8s-mcp-go
go build -o k8s-mcp-go .
MIT
Safe Kubernetes access for AI agents via MCP. Read-only by default, with explicit permission modes.
{ "mcpServers": { "io.github.kaneg-k8s-mcp-go": { "command": "mcpb", "args": [ "https://github.com/kaneg/k8s-mcp-go/releases/download/v0.4.6/k8s-mcp-go_0.4.6_darwin_amd64.mcpb" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
K8s MCP Server (Go) roda localmente via stdio.
Última verificação: 2026-11-09. Safe Kubernetes access for AI agents via MCP. Read-only by default, with explicit permission modes.