Ext Ops Panel
Open dashboard
Comparison

Rube vs io.github.KamaruSama/mcp-screenshot

Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.KamaruSama/mcp-screenshot is an MCP server published by KamaruSama. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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.KamaruSama/mcp-screenshot
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (PyPI): 98
Downloads/week (PyPI): 26
Forks (GitHub): 0
Stars (GitHub): 0
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.KamaruSama/mcp-screenshot
FactRubeio.github.KamaruSama/mcp-screenshot
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (rube.app/mcp)On your machine (mcp-screenshot)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 0
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/kamarusama/mcp-screenshot
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.KamaruSama/mcp-screenshot

In its own words, on Official MCP Registry:

Take Wayland screenshots via grim/slurp. Full screen, region, or interactive crop.

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.KamaruSama/mcp-screenshot As a local MCP server: PyPI package

Claude Code
claude mcp add --env "WAYLAND_DISPLAY=<YOUR_WAYLAND_DISPLAY>" --env "XDG_RUNTIME_DIR=<YOUR_XDG_RUNTIME_DIR>" --transport stdio mcp-screenshot -- uvx mcp-screenshot

Requires: WAYLAND_DISPLAY, XDG_RUNTIME_DIR

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.KamaruSama/mcp-screenshot asks for

  • WAYLAND_DISPLAY
  • XDG_RUNTIME_DIR

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.KamaruSama/mcp-screenshot · 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