Ext Ops Panel
Open dashboard
Comparison

Rube vs io.github.Bitfloo/mailoo

Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.Bitfloo/mailoo is an MCP server published by Bitfloo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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.Bitfloo/mailoo
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 1 370
Downloads/week (npm): 502
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.Bitfloo/mailoo
FactRubeio.github.Bitfloo/mailoo
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 (@bitfloo/mailoo)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 150, secrets among them: 5
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/bitfloo/mailoo
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.Bitfloo/mailoo

In its own words, on Official MCP Registry:

Mailoo — email MCP server for IMAP, SMTP, and ManageSieve. Multi-account, per-folder profiles.

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.Bitfloo/mailoo As a local MCP server: npm package

Claude Code
claude mcp add --env "MCP_EMAIL_ADDRESS=<YOUR_MCP_EMAIL_ADDRESS>" --env "MCP_EMAIL_ALERT_WEBHOOK_URL=<YOUR_MCP_EMAIL_ALERT_WEBHOOK_URL>" --env "MCP_EMAIL_HTTP_TOKEN=<YOUR_MCP_EMAIL_HTTP_TOKEN>" --env "MCP_EMAIL_IMAP_HOST=<YOUR_MCP_EMAIL_IMAP_HOST>" --env "MCP_EMAIL_OAUTH2_CLIENT_SECRET=<YOUR_MCP_EMAIL_OAUTH2_CLIENT_SECRET>" --env "MCP_EMAIL_OAUTH2_REFRESH_TOKEN=<YOUR_MCP_EMAIL_OAUTH2_REFRESH_TOKEN>" --env "MCP_EMAIL_PASSWORD=<YOUR_MCP_EMAIL_PASSWORD>" --env "MCP_EMAIL_SMTP_HOST=<YOUR_MCP_EMAIL_SMTP_HOST>" --transport stdio mailoo -- npx -y @bitfloo/mailoo

Requires: MCP_EMAIL_ADDRESS, MCP_EMAIL_ALERT_WEBHOOK_URL (secret), MCP_EMAIL_HTTP_TOKEN (secret), MCP_EMAIL_IMAP_HOST, MCP_EMAIL_OAUTH2_CLIENT_SECRET (secret), MCP_EMAIL_OAUTH2_REFRESH_TOKEN (secret), MCP_EMAIL_PASSWORD (secret), MCP_EMAIL_SMTP_HOST

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.Bitfloo/mailoo asks for

  • MCP_EMAIL_ACCOUNT_NAME
  • MCP_EMAIL_ADDRESS
  • MCP_EMAIL_ALERT_DESKTOP
  • MCP_EMAIL_ALERT_SOUND
  • MCP_EMAIL_ALERT_URGENCY_THRESHOLD
  • MCP_EMAIL_ALERT_WEBHOOK_ALLOW_PRIVATE
  • MCP_EMAIL_ALERT_WEBHOOK_URL (secret)
  • MCP_EMAIL_FULL_NAME
  • MCP_EMAIL_HOOK_AUTO_CALENDAR
  • MCP_EMAIL_HOOK_AUTO_FLAG
  • MCP_EMAIL_HOOK_AUTO_LABEL
  • MCP_EMAIL_HOOK_BATCH_DELAY
Show the remaining 38
  • MCP_EMAIL_HOOK_CALENDAR_ALARM_MINUTES
  • MCP_EMAIL_HOOK_CALENDAR_CONFIRM
  • MCP_EMAIL_HOOK_CALENDAR_NAME
  • MCP_EMAIL_HOOK_CUSTOM_INSTRUCTIONS
  • MCP_EMAIL_HOOK_ON_NEW_EMAIL
  • MCP_EMAIL_HOOK_PRESET
  • MCP_EMAIL_HTTP_ALLOWED_HOSTS
  • MCP_EMAIL_HTTP_HOST
  • MCP_EMAIL_HTTP_TOKEN (secret)
  • MCP_EMAIL_IMAP_DISABLE_IMAP4REV2
  • MCP_EMAIL_IMAP_HOST
  • MCP_EMAIL_IMAP_PORT
  • MCP_EMAIL_IMAP_STARTTLS
  • MCP_EMAIL_IMAP_TLS
  • MCP_EMAIL_IMAP_VERIFY_SSL
  • MCP_EMAIL_OAUTH2_CLIENT_ID
  • MCP_EMAIL_OAUTH2_CLIENT_SECRET (secret)
  • MCP_EMAIL_OAUTH2_PROVIDER
  • MCP_EMAIL_OAUTH2_REFRESH_TOKEN (secret)
  • MCP_EMAIL_PASSWORD (secret)
  • MCP_EMAIL_RATE_LIMIT
  • MCP_EMAIL_READ_ONLY
  • MCP_EMAIL_SAVE_TO_SENT
  • MCP_EMAIL_SIEVE_HOST
  • MCP_EMAIL_SIEVE_PORT
  • MCP_EMAIL_SMTP_HOST
  • MCP_EMAIL_SMTP_POOL_ENABLED
  • MCP_EMAIL_SMTP_POOL_MAX_CONNECTIONS
  • MCP_EMAIL_SMTP_POOL_MAX_MESSAGES
  • MCP_EMAIL_SMTP_PORT
  • MCP_EMAIL_SMTP_STARTTLS
  • MCP_EMAIL_SMTP_TLS
  • MCP_EMAIL_SMTP_VERIFY_SSL
  • MCP_EMAIL_SYSTEM_ONE_ENABLED
  • MCP_EMAIL_USERNAME
  • MCP_EMAIL_WATCHER_ENABLED
  • MCP_EMAIL_WATCHER_FOLDERS
  • MCP_EMAIL_WATCHER_IDLE_TIMEOUT

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.Bitfloo/mailoo · 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