rubit-mcp-mail vs JMAP Email
rubit-mcp-mail is an MCP server published by bgalmes. Marketplaces we read that list it: 1 (Official MCP Registry). JMAP Email is an MCP server published by mikluko. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  rubit-mcp-mail |  JMAP Email |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Downloads/month (PyPI): 171 Downloads/week (PyPI): 27 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.10.0 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
| Fact | rubit-mcp-mail | JMAP Email |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (rubit-mcp-mail) | On your machine (ghcr.io/mikluko/jmap-mcp:0.10.0) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/bgalmes/rubit-mcp-mail | github.com/mikluko/jmap-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
rubit-mcp-mail
Read-only MCP server for your mail — provider-agnostic IMAP that never marks a message as read.
JMAP Email
Email management via JMAP — mailboxes, messages, identities, and Sieve scripts
How to run each
rubit-mcp-mail As a local MCP server: PyPI package
claude mcp add --transport stdio rubit-mcp-mail -- uvx rubit-mcp-mail serveJMAP Email As a local MCP server: Docker image
claude mcp add --env "JMAP_AUTH_TOKEN=<YOUR_JMAP_AUTH_TOKEN>" --env "JMAP_SESSION_URL=<YOUR_JMAP_SESSION_URL>" --transport stdio jmap-mcp -- docker run -i --rm -e JMAP_AUTH_TOKEN -e JMAP_SESSION_URL ghcr.io/mikluko/jmap-mcp:0.10.0Requires: JMAP_AUTH_TOKEN (secret), JMAP_SESSION_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of rubit-mcp-mail publish no settings it asks for, so we do not compare settings.
What it can do: rubit-mcp-mail · What it can do: JMAP Email · Compare two other plugins
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.