io.github.dockndevai/mcp-openshift vs io.github.ocm-mcp-server/ocm-mcp-server
io.github.dockndevai/mcp-openshift is an MCP server published by dockndevai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ocm-mcp-server/ocm-mcp-server is an MCP server published by ocm-mcp-server. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Downloads/month (npm): 352 Downloads/week (npm): 15 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.6.0 Downloads/month (PyPI): 168 Downloads/week (PyPI): 49 Forks (GitHub): 3 Stars (GitHub): 16 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 | io.github.dockndevai/mcp-openshift | io.github.ocm-mcp-server/ocm-mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 16 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@dockndevai/mcp-openshift) | On your machine (ocm-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 2 | 3, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dockndevai/mcp-openshift | github.com/ocm-mcp-server/ocm-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
io.github.dockndevai/mcp-openshift
Safe-by-default MCP for OpenShift / Kubernetes: projects, pods, logs, deployments, routes.
io.github.ocm-mcp-server/ocm-mcp-server
Guardrailed fleet ops for AI agents: multi-cluster Kubernetes via OCM with policy, approval, audit.
How to run each
io.github.dockndevai/mcp-openshift As a local MCP server: npm package
claude mcp add --env "OPENSHIFT_PASSWORD=<YOUR_OPENSHIFT_PASSWORD>" --env "OPENSHIFT_SERVER=<YOUR_OPENSHIFT_SERVER>" --env "OPENSHIFT_TOKEN=<YOUR_OPENSHIFT_TOKEN>" --transport stdio mcp-openshift -- npx -y @dockndevai/mcp-openshift
Requires: OPENSHIFT_PASSWORD (secret), OPENSHIFT_SERVER, OPENSHIFT_TOKEN (secret)
io.github.ocm-mcp-server/ocm-mcp-server As a local MCP server: PyPI package
claude mcp add --env "KUBECONFIG=<YOUR_KUBECONFIG>" --transport stdio ocm-mcp-server -- uvx ocm-mcp-server
Requires: KUBECONFIG
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.dockndevai/mcp-openshift asks for
OPENSHIFT_CA_CERTOPENSHIFT_MODEOPENSHIFT_PASSWORD (secret)OPENSHIFT_SERVEROPENSHIFT_TOKEN (secret)OPENSHIFT_USERNAME
Only io.github.ocm-mcp-server/ocm-mcp-server asks for
KUBECONFIGOCM_MCP_HUB_CONTEXTOCM_MCP_READ_ONLY
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.dockndevai/mcp-openshift · What it can do: io.github.ocm-mcp-server/ocm-mcp-server · Compare two other plugins
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.