Ext Ops Panel
Open dashboard
Comparison

gmail-agent vs io.github.tarunlnmiit/inbox-to-action

gmail-agent is an MCP server published by dremok. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.tarunlnmiit/inbox-to-action is an MCP server published by tarunlnmiit. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
Marketplacegmail-agentio.github.tarunlnmiit/inbox-to-action
Official MCP Registry Listed
Version: 0.3.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 65
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.2.11
Downloads/month (PyPI): 164
Downloads/week (PyPI): 27
Forks (GitHub): 0
Stars (GitHub): 3
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-agent vs io.github.tarunlnmiit/inbox-to-action
Factgmail-agentio.github.tarunlnmiit/inbox-to-action
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)3 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (gmail-agent)On your machine (inbox-to-action)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 0Not published
LicenceNot statedNot stated
Repository (differs)github.com/dremok/gmail-agentgithub.com/tarunlnmiit/inbox-to-action
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

gmail-agent

In its own words, on Official MCP Registry:

Gmail for AI agents: search, read, download attachments, send, reply, drafts, labels.

io.github.tarunlnmiit/inbox-to-action

In its own words, on Official MCP Registry:

Agentic Gmail triage: classify, summarize, extract tasks, draft replies. Never sends.

How to run each

gmail-agent As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio gmail-agent -- uvx gmail-agent mcp

io.github.tarunlnmiit/inbox-to-action As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio inbox-to-action -- uvx inbox-to-action mcp

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 io.github.tarunlnmiit/inbox-to-action publish no settings it asks for, so we do not compare settings.

What it can do: gmail-agent · What it can do: io.github.tarunlnmiit/inbox-to-action · 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