Ext Ops Panel
Open dashboard
Comparison

Kubectl vs io.github.mikhae1/kubeview

Kubectl is an MCP server published by rohitg00. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.mikhae1/kubeview is an MCP server published by mikhae1. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. 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

Where each is published
MarketplaceKubectlio.github.mikhae1/kubeview
Docker MCP Catalog Listed
Version: sha256:a6bf30877095
Forks (GitHub): 186
Pulls (Docker Hub): 26 969
Stars (Docker Hub): 0
Stars (GitHub): 964
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.3.0
Downloads/month (npm): 2 567
Downloads/week (npm): 282
Forks (GitHub): 2
Stars (GitHub): 5
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.3.0
Downloads/month (npm): 2 567
Downloads/week (npm): 282
Forks (GitHub): 2
Stars (GitHub): 5
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

Kubectl vs io.github.mikhae1/kubeview
FactKubectlio.github.mikhae1/kubeview
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)964 (better)5 (worse)
Pulls (Docker Hub) (differs)26 969No figure on Docker Hub
Forks (GitHub) (differs)186 (better)2 (worse)
Last release (differs)Not published2026-10-18
Where it runs (differs)On your machine (mcp/kubectl-mcp-server)On your machine (kubeview-mcp)
Transportstdiostdio
Tools it declares (differs)26Not published
Environment variables it asks for (differs)Not published24, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/rohitg00/kubectl-mcp-servergithub.com/mikhae1/kubeview-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

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

Kubectl

In its own words, on Docker MCP Catalog:

MCP Server that enables AI assistants to interact with Kubernetes clusters via kubectl operations.

io.github.mikhae1/kubeview

In its own words, on Official MCP Registry:

Read-only Model Context Protocol MCP server enabling code-driven AI analysis of Kubernetes clusters.

How to run each

Kubectl As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio kubectl-mcp-server -- docker run -i --rm mcp/kubectl-mcp-server

io.github.mikhae1/kubeview As a local MCP server: npm package

Claude Code
claude mcp add --env "MCP_APPROVAL_STATE_SECRET=<YOUR_MCP_APPROVAL_STATE_SECRET>" --transport stdio kubeview -- npx -y kubeview-mcp

Requires: MCP_APPROVAL_STATE_SECRET (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of io.github.mikhae1/kubeview publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Kubectl publish no settings it asks for, so we do not compare settings.

What it can do: Kubectl · What it can do: io.github.mikhae1/kubeview · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built