Gmail vs google-workspace-webhooks
Gmail is an MCP server published by Sallytion. Marketplaces we read that list it: 1 (Docker MCP Catalog). google-workspace-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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 |  Gmail | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9d806c6ba375 Forks (GitHub): 9 Stars (GitHub): 12 Not marked · First seen |
Not listed |
| Community marketplace hookdeck/webhook-skills | Not listed | Listed Version: not stated No figure published 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 | Gmail | google-workspace-webhooks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 | No figure on GitHub |
| Forks (GitHub) (differs) | 9 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (yashtekwani/gmail-mcp) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 1 | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/sallytion/gmail-mcp | github.com/hookdeck/webhook-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-21 |
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
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.
google-workspace-webhooks
Receive and verify Google Workspace push notifications (webhooks) from Google Drive, Google Calendar, and the Admin SDK Directory API. Use when setting up a watch channel webhook receiver (files.watch, changes.watch, events.watch, users.watch), verifying the X-Goog-Channel-Token header, answering the initial sync message, handling X-Goog-Resource-State values (sync, add, update, remove, trash, untrash, change, exists, not_exists), or renewing expiring channels.
How to run each
Gmail As a local MCP server: Docker image
claude mcp add --env "EMAIL_PASSWORD=<YOUR_EMAIL_PASSWORD>" --transport stdio gmail-mcp -- docker run -i --rm -e EMAIL_PASSWORD yashtekwani/gmail-mcpRequires: EMAIL_PASSWORD (secret)
google-workspace-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install google-workspace-webhooks@webhook-skillsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of google-workspace-webhooks publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of google-workspace-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: Gmail · What it can do: google-workspace-webhooks · 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.