What it does & operational scope
Kubernetes MCP Server translates model instructions into structured Kubernetes API calls over local stdio transport. Reading cluster authentication from the local kubeconfig file, it provides endpoints to inspect pods, stream container logs, analyze failing rollout statuses, query Custom Resource Definitions (CRDs), and evaluate YAML manifests against live clusters.
Kubernetes MCP Server is an open-source Model Context Protocol server licensed under MIT that exposes Kubernetes pod inspection, container log analysis, and manifest verification over local stdio.
Your AI coding agent requires live access to Kubernetes tools and resources over local IPC or streamable transport.
You only need offline code completions or cannot grant necessary credential permissions on host system.
Client configuration & wire setup
Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.
claude_desktop_config.json{ "mcpServers": { "kubernetes": { "command": "npx", "args": ["-y", "mcp-server-kubernetes"] } }}Exposed tool endpoints & primitives
Discovered MCP Tools
4 Tools Readylist_pods🟢 Read-Only (Safe)Enumerate active pods, namespaces, phase status, and node assignments
get_pod_logs🟢 Read-Only (Safe)Stream container stdout/stderr log output from specified pod and namespace
describe_resource🟢 Read-Only (Safe)Retrieve detailed Kubernetes object manifests, events, and condition arrays
apply_manifest🟡 State MutationApply YAML or JSON Kubernetes resource manifest against active cluster
Scopes, secret storage, and sandbox boundaries
Run Kubernetes MCP Server with scoped environment tokens. Never run under root and restrict network ingress.Real conversational prompts & expected tool calls
💬 "Find latest technical updates for Kubernetes MCP Server from the last 7 days"list_pods({ query: "Kubernetes MCP Server updates", limit: 5 })Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.
💬 "Inspect status and health boundaries for Kubernetes MCP Server"list_pods_status({ verbose: true })Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.
Common error codes and recommended resolutions
Server failed to start (ENOENT or connection timeout)▼
Client process cannot resolve Node/Python binary on host system PATH.
Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").
Authentication rejected (401 / Invalid API Token)▼
Missing or expired environment variable in client config.
Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.
Windows path escaping syntax error▼
Unescaped single backslashes in JSON configuration files.
Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").
Technical trade-offs and operational friction
+ Translates cluster debugging inquiries into precise API calls without kubectl terminal typing.
+ Filters log output by container name and tail limits to save model tokens.
+ Works out of the box with existing cloud provider kubeconfig configurations.
− Lacks built-in dry-run validation gates, meaning an agent operating with cluster-admin kubeconfig credentials can accidentally delete live deployments or evict pods.
− Massive JSON payloads returned by cluster resource queries saturate token limits when evaluating namespaces containing dozens of active pods.
Side-by-side rival comparisons
Compare Kubernetes MCP Server vs Docker MCP Server across transport protocols and exposed tools.
Enter ShowdownJSON-RPC 2.0 wire trace & receipts
Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
1{2 "jsonrpc": "2.0",3 "id": 1,4 "method": "tools/call",5 "params": {6 "name": "inspect",7 "arguments": {}8 }9}
