Ext Ops Panel
Open dashboard
Comparison

Rube vs X (Twitter)

Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). X (Twitter) is an MCP server published by Role1776. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceRubeX (Twitter)
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.1
Forks (GitHub): 0
Stars (GitHub): 2
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 X (Twitter)
FactRubeX (Twitter)
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (rube.app/mcp)On your machine (ghcr.io/role1776/mcp-x:0.1.1)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 141, secrets among them: 4
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/role1776/mcp-x
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.

X (Twitter)

In its own words, on Official MCP Registry:

Search, read and publish X posts and manage users, lists and media via the X API v2.

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)

X (Twitter) As a local MCP server: Docker image

Claude Code
claude mcp add --env "MEDIA_ROOT=<YOUR_MEDIA_ROOT>" --env "X_ACCESS_TOKEN=<YOUR_X_ACCESS_TOKEN>" --env "X_ACCESS_TOKEN_SECRET=<YOUR_X_ACCESS_TOKEN_SECRET>" --env "X_API_KEY=<YOUR_X_API_KEY>" --env "X_API_KEY_SECRET=<YOUR_X_API_KEY_SECRET>" --transport stdio mcp-x -- docker run -i --rm -e MEDIA_ROOT -e X_ACCESS_TOKEN -e X_ACCESS_TOKEN_SECRET -e X_API_KEY -e X_API_KEY_SECRET ghcr.io/role1776/mcp-x:0.1.1

Requires: MEDIA_ROOT, X_ACCESS_TOKEN (secret), X_ACCESS_TOKEN_SECRET (secret), X_API_KEY (secret), X_API_KEY_SECRET (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 X (Twitter) asks for

  • LISTS_DEFAULT_RESULTS
  • LISTS_DEFAULT_TIMEOUT_MS
  • LISTS_MAX_RESULTS
  • LISTS_MAX_TIMEOUT_MS
  • LISTS_MIN_TIMEOUT_MS
  • LOG_MODE
  • MAX_IDLE_CONNS_PER_HOST
  • MCP_NAME
  • MCP_PATH
  • MCP_TRANSPORT
  • MEDIA_CHUNK_BYTES
  • MEDIA_DEFAULT_TIMEOUT_MS
Show the remaining 29
  • MEDIA_MAX_TIMEOUT_MS
  • MEDIA_MIN_TIMEOUT_MS
  • MEDIA_POLL_INTERVAL_MS
  • MEDIA_ROOT
  • POSTS_DEFAULT_DAYS
  • POSTS_DEFAULT_RESULTS
  • POSTS_DEFAULT_TIMEOUT_MS
  • POSTS_MAX_DAYS
  • POSTS_MAX_IDS
  • POSTS_MAX_QUERIES
  • POSTS_MAX_RESULTS
  • POSTS_MAX_TIMEOUT_MS
  • POSTS_MAX_USERNAMES
  • POSTS_MIN_TIMEOUT_MS
  • SERVER_PORT
  • SERVER_READ_TIMEOUT
  • SERVER_WRITE_TIMEOUT
  • USERS_DEFAULT_RESULTS
  • USERS_DEFAULT_TIMEOUT_MS
  • USERS_MAX_IDS
  • USERS_MAX_RESULTS
  • USERS_MAX_TIMEOUT_MS
  • USERS_MAX_USERNAMES
  • USERS_MIN_TIMEOUT_MS
  • X_ACCESS_TOKEN (secret)
  • X_ACCESS_TOKEN_SECRET (secret)
  • X_API_KEY (secret)
  • X_API_KEY_SECRET (secret)
  • X_DEBUG

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

What it can do: Rube · What it can do: X (Twitter) · 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