MCP Server Kubernetes

MCP Server Kubernetes (mcp-server-kubernetes) by Flux159 is a Model Context Protocol server that exposes a kubectl- and Helm-shaped toolset to any MCP-compatible client, so an AI assistant like Claude Desktop, Claude Code, Cursor, VS Code Copilot or Codex CLI can inspect and manage a real Kubernetes cluster through natural-language prompts. It reads the local kubeconfig, so whatever context and RBAC the operator already has, the model gets. Once wired up, the assistant can get / list / describe / create / apply / delete / patch arbitrary resources, tail and grep pod logs, exec commands inside containers, drive rollouts and scale deployments, cordon and drain nodes, port-forward services, and clean up pods stuck in bad phases. Helm v3 is a first-class citizen: install, upgrade, uninstall and template charts with custom values files. A built-in /k8s-diagnose prompt walks the model through a systematic pod-troubleshooting flow (events, describe, logs, previous logs, related resources), which is where the project really earns its keep for on-call and platform engineers. For safety the server ships a non-destructive mode that hides mutating tools, plus secrets masking so credential values do not leak back into the chat transcript, and optional OpenTelemetry tracing so every tool call the model makes is auditable. Installation is a single npx invocation, distributed as a TypeScript/Node package on npm, and the codebase is MIT-licensed on GitHub with an active release cadence and a large fork community. It suits SREs, platform teams and Kubernetes-heavy developers who want an LLM copilot for day-2 operations without building their own tooling layer, and who are comfortable trusting an agent with cluster credentials at the permission level the kubeconfig grants.