Rube vs Steamworks Release Assistant
Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Steamworks Release Assistant is an MCP server published by wazzapsenk. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-26. 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 |  Rube |  Steamworks Release Assistant |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 Downloads/month (PyPI): 274 Downloads/week (PyPI): 199 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.4.0 Downloads/month (PyPI): 274 Downloads/week (PyPI): 199 Forks (GitHub): 0 Stars (GitHub): 8 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 | Steamworks Release Assistant |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 8 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | Remote server (rube.app/mcp) | On your machine (steamworks-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/wazzapsenk/steamworks-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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.
Steamworks Release Assistant
Put a game on Steam: store page, achievements, Valve-rule checks, market data, Steamworks.
How to run each
Rube As a remote MCP server
claude mcp add --transport http rube https://rube.app/mcpRequires: RUBE_API_KEY (secret)
Steamworks Release Assistant As a local MCP server: PyPI package
claude mcp add --env "STEAMWORKS_PUBLISHER_KEY=<YOUR_STEAMWORKS_PUBLISHER_KEY>" --transport stdio steamworks-mcp -- uvx steamworks-mcpRequires: STEAMWORKS_PUBLISHER_KEY (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 Steamworks Release Assistant asks for
STEAMWORKS_MCP_ROOTSTEAMWORKS_PUBLISHER_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Rube · What it can do: Steamworks Release Assistant · 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 Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.