Pear MCP vs Google Workspace
Pear MCP is an MCP server published by AshtonAU. Marketplaces we read that list it: 1 (Official MCP Registry). Google Workspace is an MCP server published by aaronsb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  Pear MCP |  Google Workspace |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 4.8.0 Downloads/month (npm): 5 596 Downloads/week (npm): 920 Forks (GitHub): 56 Stars (GitHub): 192 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 | Pear MCP | Google Workspace |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 192 |
| Forks (GitHub) (differs) | No figure on GitHub | 56 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Remote server (pearmcp.com/api/mcp) | On your machine (@aaronsb/google-workspace-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/aaronsb/google-workspace-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | 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
Pear MCP
Connect Apple iCloud and Microsoft 365 mail, calendars, contacts and tasks to AI.
Google Workspace
Give AI agents access to Gmail, Calendar, Drive, and more — multi-account, manifest-driven
How to run each
Pear MCP As a remote MCP server
claude mcp add --transport http pear https://pearmcp.com/api/mcpGoogle Workspace As a local MCP server: npm package
claude mcp add --transport stdio google-workspace -- npx -y @aaronsb/google-workspace-mcpCommands 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 Pear MCP publish no settings it asks for, so we do not compare settings.
What it can do: Pear MCP · What it can do: Google Workspace · 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.