Google Contacts vs Google Workspace
Google Contacts is an MCP server published by domdomegg. Marketplaces we read that list it: 1 (Official MCP Registry). Google Workspace is an MCP server published by mindstone. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  Google Contacts |  Google Workspace |
|---|---|---|
| Official MCP Registry | Listed Version: 1.3.0 Downloads/month (npm): 481 Downloads/week (npm): 125 Forks (GitHub): 2 Stars (GitHub): 5 Not marked · First seen |
Listed Version: 0.5.5 Downloads/month (npm): 4 481 Downloads/week (npm): 848 Forks (GitHub): 4 Stars (GitHub): 14 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 | Google Contacts | Google Workspace |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 (worse) | 14 (better) |
| Forks (GitHub) (differs) | 2 (worse) | 4 (better) |
| Last release (differs) | Not published | 2026-11-06 |
| Where it runs (differs) | On your machine (google-contacts-mcp) | On your machine (@mindstone/mcp-server-google-workspace) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | 9, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/domdomegg/google-contacts-mcp | github.com/mindstone/mcp-servers |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen | 2026-10-11 | 2026-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
Google Contacts
Allow AI systems to list, search, and manage contacts via Google Contacts.
Google Workspace
Google Workspace MCP server for Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, and more
How to run each
Google Contacts As a local MCP server: npm package
claude mcp add --env "GOOGLE_ACCESS_TOKEN=<YOUR_GOOGLE_ACCESS_TOKEN>" --env "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "MCP_TRANSPORT=<YOUR_MCP_TRANSPORT>" --transport stdio google-contacts-mcp -- npx -y google-contacts-mcpRequires: GOOGLE_ACCESS_TOKEN (secret), GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), MCP_TRANSPORT
Google Workspace As a local MCP server: npm package
claude mcp add --env "ACCOUNTS_PATH=<YOUR_ACCOUNTS_PATH>" --env "CREDENTIALS_PATH=<YOUR_CREDENTIALS_PATH>" --env "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --transport stdio mcp-server-google-workspace -- npx -y @mindstone/mcp-server-google-workspaceRequires: ACCOUNTS_PATH, CREDENTIALS_PATH, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret)
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
Only Google Contacts asks for
GOOGLE_ACCESS_TOKEN (secret)MCP_TRANSPORT
Only Google Workspace asks for
ACCOUNTS_PATHCREDENTIALS_PATHGAUTH_FILEGOOGLE_WORKSPACE_DISABLE_REFRESHGOOGLE_WORKSPACE_REQUEST_TIMEOUT_MSMCP_WORKSPACE_PATHWORKSPACE_BASE_PATH
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Google Contacts · 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.