Side-by-side comparison

Despite nearly equal star counts (1,294 vs 1,355), containers leads in score (84.62 vs 79.65). The gap is driven by freshness — containers committed March 16 vs Flux159's March 1, an 18-day difference that impacts the freshness signal (25% of the score). Both have 40+ contributors, making them the most deeply staffed tools in the Kubernetes category.

Data from March 19, 2026 crawl. Score = composite of stars 15%, freshness 25%, issue health 25%, contributors 10%, inbound dependents 25%.

containers/kubernetes-mcp-server deep dive

containers/kubernetes-mcp-server — score 84.62

containers/kubernetes-mcp-server is maintained under the containers GitHub organization — the same org behind Podman, Buildah, and other container-ecosystem tools. Written in Go with an Apache-2.0 license, it is the more "enterprise-ready" of the two options.

The standout feature is OpenShift support. OpenShift is Red Hat's Kubernetes distribution used heavily in regulated industries and large enterprises. If your organization runs OpenShift, this is the only Kubernetes MCP server with native support for OpenShift-specific APIs and resource types.

42 contributors is the highest in the Kubernetes category. The issue health signal reflects a responsive team: 98 issues closed against 77 open (a 56% close rate). Go's performance characteristics matter less for an MCP server than for a high-throughput service — but the language choice reflects the containers org's ecosystem preferences.

Flux159/mcp-server-kubernetes deep dive

Flux159/mcp-server-kubernetes — score 79.65

Flux159/mcp-server-kubernetes is the most-starred Kubernetes MCP server (1,355 stars vs 1,294 for containers). Written in TypeScript with an MIT license, it is the friendlier option for JavaScript/TypeScript ecosystems and for teams that want the permissive MIT license without the Apache-2.0 patent clauses.

The 11 inbound dependents in the AgentRank index suggest that other MCP servers and agent frameworks import or build on top of it — a meaningful indicator of ecosystem traction. The MIT license makes it easy to embed in commercial products without attribution requirements.

The lower score (79.65) is primarily driven by the March 1 commit date — it is 18 days staler than containers as of the March 19 crawl. Issue health is strong: 83 closed issues against 11 open, an 88% close rate — the best in this comparison, and one of the best in the DevOps category overall.

Verdict

Both servers are mature, well-maintained, and appropriate for production use. The decision criteria are narrow:

• You run OpenShift: containers/kubernetes-mcp-server — only option with native OpenShift support. Score 84.62.
• You want TypeScript or MIT license: Flux159/mcp-server-kubernetes — TypeScript, MIT, 88% issue close rate. Score 79.65.
• You're building on top of a k8s MCP server: Flux159 has 11 inbound dependents vs 0 for containers — the more commonly embedded option.
• Standard vanilla k8s, no preference: containers leads on current score (84.62) and freshness. Default to it unless you have a specific reason to prefer Flux159.

Setup guide

Install containers/kubernetes-mcp-server

Add to your MCP client config — requires Go or a pre-built binary:

{
  "mcpServers": {
    "kubernetes": {
      "command": "kubernetes-mcp-server",
      "args": [],
      "env": {
        "KUBECONFIG": "/path/to/.kube/config"
      }
    }
  }
}

Install Flux159/mcp-server-kubernetes

{
  "mcpServers": {
    "kubernetes": {
      "command": "npx",
      "args": ["-y", "mcp-server-kubernetes"],
      "env": {
        "KUBECONFIG": "/path/to/.kube/config"
      }
    }
  }
}

Both servers use your local kubeconfig for cluster access. Ensure your kubectl context points to the correct cluster before starting.