Install mcp-server-kubernetes with Homebrew

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• mcp-server-kubernetes

Project history

The repository was created in December 2024, during the first large wave of MCP servers that mapped existing command-line administration domains into agent-callable tools. Its README describes a server that connects to a Kubernetes cluster and loads kubeconfig from multiple sources.

The project expanded beyond basic kubectl commands into advanced operations, prompts, observability, secrets masking, and safety modes. The advanced README documents authentication priority order, custom kubeconfig paths, environment-based cluster credentials, read-only mode, and non-destructive mode.

Adoption history

The server is packaged for use through `npx mcp-server-kubernetes`, Homebrew, and client-specific integrations such as Claude Code, Claude Desktop, VS Code, Cursor, Gemini CLI extensions, and mcpb packages. This broad installation documentation reflects the package's role as infrastructure glue rather than a single-client demo.

GitHub metadata showed more than a thousand stars and hundreds of forks by July 2026, and release metadata showed continued 3.x releases in 2026. The project also links to ecosystem badges and MCP catalog listings, reinforcing that it is a packaged server intended for discovery and reuse.

How it is used

Users must have `kubectl`, a valid kubeconfig, cluster access, and optionally Helm v3 in PATH. By default, the server loads credentials from `~/.kube/config`, while advanced options allow full kubeconfig YAML or JSON, server/token environment variables, in-cluster config, `KUBECONFIG_PATH`, or the standard `KUBECONFIG` variable.

Typical client usage is a stdio command such as `npx mcp-server-kubernetes`. Operators can enable read-only or non-destructive modes through environment variables when connecting production or shared clusters.

Why package nerds care

mcp-server-kubernetes is notable because it packages a high-stakes existing CLI domain rather than a toy MCP demo. The value for package users is in reusing the local Kubernetes credential model and command-line tools while exposing them through MCP.

It also illustrates why package metadata matters for MCP servers: a cluster-management server needs clear docs around credentials, safety modes, dependencies, and client configuration so users understand what a one-line `npx` or Homebrew install is allowed to do.

Timeline

• 2024: GitHub repository created for Flux159/mcp-server-kubernetes.
• 2025: README documents kubectl, Helm, client configuration, and advanced cluster operations.
• 2025: Advanced README documents authentication priority order and safety modes.
• 2026: 3.x releases continue, including v3.9.2 in June 2026.

Related projects

• Kubernetes and kubectl provide the underlying cluster-management model.
• Helm is used for optional chart operations.
• Flux159/mcp-chat is documented as a CLI chat client that can interact with the server.

Sources

• https://api.github.com/repos/Flux159/mcp-server-kubernetes
• https://api.github.com/repos/Flux159/mcp-server-kubernetes/releases
• https://github.com/Flux159/mcp-server-kubernetes
• https://github.com/Flux159/mcp-server-kubernetes#readme
• https://github.com/Flux159/mcp-server-kubernetes/blob/main/ADVANCED_README.md