Ext Ops Panel
Open dashboard
Comparison

Gmail vs EML Toolkit

Gmail is an MCP server published by Sallytion. Marketplaces we read that list it: 1 (Docker MCP Catalog). EML Toolkit is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
MarketplaceGmailEML Toolkit
Docker MCP Catalog Listed
Version: sha256:9d806c6ba375
Forks (GitHub): 9
Stars (GitHub): 12
Not marked · First seen
Not listed
Community marketplace danielrosehill/claude-code-plugins Not listed Listed
Version: 0.1.0
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 EML Toolkit
FactGmailEML Toolkit
Marketplaces that list it11
Stars (GitHub) (differs)12 (better)0 (worse)
Forks (GitHub) (differs)9 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (yashtekwani/gmail-mcp)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)3Not published
Environment variables it asks for (differs)6, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle6
Licence (differs)Not statedMIT
Repository (differs)github.com/sallytion/gmail-mcpgithub.com/danielrosehill/claude-eml-toolkit
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15

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 Docker MCP Catalog:

A Model Context Protocol server for Gmail operations using IMAP/SMTP with app password authentication. Supports listing messages, searching emails, and sending messages. To create your app password, visit your Google Account settings under Security > App Passwords. Or visit the link https://myaccount.google.com/apppasswords.

EML Toolkit

In its own words, on Community GitHub marketplaces:

Process .eml email exports — reconstruct a thread from loose .eml files, render the chain to a single PDF with correct right-to-left handling for Hebrew and Arabic, extract attachments, export Markdown, redact before sharing, and build numbered evidence bundles.

How to run each

Gmail As a local MCP server: Docker image

Claude Code
claude mcp add --env "EMAIL_PASSWORD=<YOUR_EMAIL_PASSWORD>" --transport stdio gmail-mcp -- docker run -i --rm -e EMAIL_PASSWORD yashtekwani/gmail-mcp

Requires: EMAIL_PASSWORD (secret)

EML Toolkit As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install eml-toolkit@danielrosehill

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

Tools each declares

The marketplaces of EML Toolkit publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Gmail · What it can do: EML Toolkit · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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