Rube vs wallabag MCP
Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). wallabag MCP is an MCP server published by rusty4444. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  wallabag MCP | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (PyPI): 59 Downloads/week (PyPI): 12 Forks (GitHub): 4 Stars (GitHub): 3 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 | Rube | wallabag MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 3 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (rube.app/mcp) | On your machine (wallabag-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 6, secrets among them: 3 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/rusty4444/wallabag-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-14 | no 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
Access to Rube's catalog of remote MCP servers.
wallabag MCP
MCP server for wallabag read-it-later entries, tags, and annotations.
How to run each
Rube As a remote MCP server
claude mcp add --transport http rube https://rube.app/mcpRequires: RUBE_API_KEY (secret)
wallabag MCP As a local MCP server: PyPI package
claude mcp add --env "WALLABAG_ACCESS_TOKEN=<YOUR_WALLABAG_ACCESS_TOKEN>" --env "WALLABAG_BASE_URL=<YOUR_WALLABAG_BASE_URL>" --env "WALLABAG_CLIENT_SECRET=<YOUR_WALLABAG_CLIENT_SECRET>" --env "WALLABAG_PASSWORD=<YOUR_WALLABAG_PASSWORD>" --transport stdio wallabag-mcp -- uvx wallabag-mcpRequires: WALLABAG_ACCESS_TOKEN (secret), WALLABAG_BASE_URL, WALLABAG_CLIENT_SECRET (secret), WALLABAG_PASSWORD (secret)
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 wallabag MCP asks for
WALLABAG_ACCESS_TOKEN (secret)WALLABAG_BASE_URLWALLABAG_CLIENT_IDWALLABAG_CLIENT_SECRET (secret)WALLABAG_PASSWORD (secret)WALLABAG_USERNAME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Rube · What it can do: wallabag 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.