Ext Ops Panel
Open dashboard
Comparison

AI Inbx Inbox vs com.mcparmory/google-gmail

AI Inbx Inbox is an MCP server published by aiinbx.com. Marketplaces we read that list it: 1 (Official MCP Registry). com.mcparmory/google-gmail is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceAI Inbx Inboxcom.mcparmory/google-gmail
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.4
Downloads/month (PyPI): 825
Downloads/week (PyPI): 155
Forks (GitHub): 4
Stars (GitHub): 32
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

AI Inbx Inbox vs com.mcparmory/google-gmail
FactAI Inbx Inboxcom.mcparmory/google-gmail
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub32
Forks (GitHub) (differs)No figure on GitHub4
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.aiinbx.com/inbox)On your machine (mcparmory-google-gmail)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/mcparmory/registry
Changes in the last 7 days (differs)20
First seen (differs)2026-11-032026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 405no 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

AI Inbx Inbox

In its own words, on Official MCP Registry:

Give Claude, Cursor or any agent its own email address: send, read and reply in threads.

com.mcparmory/google-gmail

In its own words, on Official MCP Registry:

Send, read, organize emails, manage labels, drafts, and filters

How to run each

AI Inbx Inbox As a remote MCP server

Claude Code
claude mcp add --transport http inbox https://mcp.aiinbx.com/inbox

com.mcparmory/google-gmail As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio google-gmail -- uvx mcparmory-google-gmail

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

Only AI Inbx Inbox 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

Neither one's marketplaces publish the settings it asks for.

What it can do: AI Inbx Inbox · What it can do: com.mcparmory/google-gmail · 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.

Where the data comes from: how the catalog is built