Kubernetes vs Helm chart.yaml name shape, body discarded
Kubernetes is an MCP server published by Flux159. Marketplaces we read that list it: 1 (Docker MCP Catalog). Helm chart.yaml name shape, body discarded is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Kubernetes |  Helm chart.yaml name shape, body discarded |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:5ffbf7f0a8aa Forks (GitHub): 284 Pulls (Docker Hub): 335 375 Stars (Docker Hub): 20 Stars (GitHub): 1 606 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Kubernetes | Helm chart.yaml name shape, body discarded |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 606 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 335 375 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 284 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/kubernetes) | Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/helm-chart-ok/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 23 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/flux159/mcp-server-kubernetes | github.com/sadri-dridi/named-mcp-utilities |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 17 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Kubernetes
Connect to a Kubernetes cluster and manage it.
Helm chart.yaml name shape, body discarded
Helm chart.yaml name shape, body discarded
How to run each
Kubernetes As a local MCP server: Docker image
claude mcp add --transport stdio kubernetes -- docker run -i --rm mcp/kubernetesHelm chart.yaml name shape, body discarded As a remote MCP server
claude mcp add --transport http helm-chart-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/helm-chart-ok/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Helm chart.yaml name shape, body discarded has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Helm chart.yaml name shape, body discarded publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Kubernetes · What it can do: Helm chart.yaml name shape, body discarded · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.