Ext Ops Panel
Open dashboard
Comparison

Rube vs io.github.cameronrye/openzim-mcp

Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.cameronrye/openzim-mcp is an MCP server published by cameronrye. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceRubeio.github.cameronrye/openzim-mcp
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.3.4
Downloads/month (PyPI): 1 496
Downloads/week (PyPI): 300
Forks (GitHub): 15
Stars (GitHub): 145
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

Rube vs io.github.cameronrye/openzim-mcp
FactRubeio.github.cameronrye/openzim-mcp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub145
Forks (GitHub) (differs)No figure on GitHub15
Last releaseNot publishedNot published
Where it runs (differs)Remote server (rube.app/mcp)On your machine (openzim-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/cameronrye/openzim-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-14no remote endpoint we check

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

Rube

In its own words, on Docker MCP Catalog:

Access to Rube's catalog of remote MCP servers.

io.github.cameronrye/openzim-mcp

In its own words, on Official MCP Registry:

Offline MCP access to ZIM knowledge archives — Wikipedia, Wiktionary, Stack Exchange, Kiwix.

How to run each

Rube As a remote MCP server

Claude Code
claude mcp add --transport http rube https://rube.app/mcp

Requires: RUBE_API_KEY (secret)

io.github.cameronrye/openzim-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio openzim-mcp -- uvx openzim-mcp "<YOUR_ZIM_DIRECTORY>"

Requires: <zim_directory>

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

Only Rube has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Rube asks for

  • RUBE_API_KEY (secret)

Only io.github.cameronrye/openzim-mcp asks for

  • OPENZIM_MCP_TOOL_MODE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Rube · What it can do: io.github.cameronrye/openzim-mcp · 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.

Where the data comes from: how the catalog is built