Ext Ops Panel
Open dashboard
Comparison

Gmail vs com.mambabuilt/mcp-email-waterfall-orchestrator

Gmail is a plugin bundle for AI coding tools published by OpenAI. Marketplaces we read that list it: 1 (Codex: openai-curated (openai/plugins)). com.mambabuilt/mcp-email-waterfall-orchestrator is an MCP server published by mambabuilt.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
MarketplaceGmailcom.mambabuilt/mcp-email-waterfall-orchestrator
Codex: openai-curated (openai/plugins) Listed
Version: 0.1.9
Forks (GitHub): 973
Stars (GitHub): 7 607
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.0
Downloads/month (npm): 395
Downloads/week (npm): 36
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

Gmail vs com.mambabuilt/mcp-email-waterfall-orchestrator
FactGmailcom.mambabuilt/mcp-email-waterfall-orchestrator
Marketplaces that list it11
Stars (GitHub) (differs)7 607 (better)0 (worse)
Forks (GitHub) (differs)973 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (gmailmcp.googleapis.com/mcp/v1)On your machine (@mambalabsdev/mcp-email-waterfall-orchestrator)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/openai/pluginsgithub.com/mambalabsdev/mcp-email-waterfall-orchestrator
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-24no 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

Gmail

In its own words, on Codex: openai-curated (openai/plugins):

Work with Gmail using the configured Gmail app connector.

com.mambabuilt/mcp-email-waterfall-orchestrator

In its own words, on Official MCP Registry:

Finds and verifies work emails on your own provider keys, with real per-provider spend.

How to run each

Gmail As a Codex plugin

Codex
codex plugin marketplace add openai/plugins

com.mambabuilt/mcp-email-waterfall-orchestrator As a local MCP server: npm package

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio mcp-email-waterfall-orchestrator -- npx -y @mambalabsdev/mcp-email-waterfall-orchestrator

Requires: APIFY_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Gmail 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

The marketplaces of Gmail publish no settings it asks for, so we do not compare settings.

What it can do: Gmail · What it can do: com.mambabuilt/mcp-email-waterfall-orchestrator · Compare two other plugins

Data comes from the public marketplace file https://github.com/openai/plugins/blob/HEAD/.agents/plugins/marketplace.json. 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