ParseAddr — Address Parsing & Normalization vs Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token
ParseAddr — Address Parsing & Normalization is an MCP server published by parseaddr.com. Marketplaces we read that list it: 1 (Official MCP Registry). Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token is an MCP server published by adelaidasofia. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-23. 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 |  ParseAddr — Address Parsing & Normalization |  Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 3 Stars (GitHub): 3 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.1.0 Forks (GitHub): 3 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
| Fact | ParseAddr — Address Parsing & Normalization | Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 3 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.parseaddr.com/mcp) | On your machine (https://github.com/adelaidasofia/google-workspace-mcp/releases/download/v0.1.0/google-workspace-mcp.mcpb) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/wezpyke/parseaddr-mcp | github.com/adelaidasofia/google-workspace-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no 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
ParseAddr — Address Parsing & Normalization
Hosted libpostal: messy free-text postal addresses → structured fields. No 2-4GB self-host.
Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token
Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token-efficient, macOS…
How to run each
ParseAddr — Address Parsing & Normalization As a remote MCP server
claude mcp add --transport http address-parse https://api.parseaddr.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install google-workspace-mcp@claude-communityRequires: GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ParseAddr — Address Parsing & Normalization 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 ParseAddr — Address Parsing & Normalization publish no settings it asks for, so we do not compare settings.
What it can do: ParseAddr — Address Parsing & Normalization · What it can do: Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.