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.

What makes it different

• Read-only by default: useful for diagnosis without giving AI permission to mutate the cluster.
• Explicit permission modes: choose readonly, readwrite, or dangerous before the assistant starts.
• No Docker required: install via MCPB bundles or a single native binary.
• Kubernetes-native visibility: inspect pods, deployments, services, logs, events, nodes, and live CPU/memory usage.
• Registry-ready distribution: published as io.github.kaneg/k8s-mcp-go for MCP Registry consumers and packaged clients.

Distribution

• MCP Registry: published as io.github.kaneg/k8s-mcp-go.
• PulseMCP: indexed from the MCP ecosystem with the official server.json.
• Claude Code Marketplaces: listed with MCPB installation metadata.

Why

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:

• delete the wrong resource
• restart the wrong workload
• apply a dangerous change
• turn a debugging session into a production incident

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?

Permission Modes

You choose the boundary up front:

readonly (default)

For diagnosis, inspection, and safe exploration.

AI can do things like:

• list pods, deployments, services, nodes, and namespaces
• read logs and events
• inspect cluster state
• check resource usage

It cannot modify workloads or delete resources.

readwrite

For controlled operational workflows.

AI can do things like:

• scale deployments
• restart deployments
• restart statefulsets
• update images
• patch deployments
• create namespaces

It still cannot perform the most destructive operations.

dangerous

Full access.

Use this only when you explicitly want AI to be able to:

• delete resources
• delete namespaces
• apply arbitrary YAML

If you are unsure, use readonly.

Quick Start

Option 1: MCPB Install (Recommended)

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.

Option 2: Manual Binary Install

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 MC

... View full README on GitHub