Omi vs Google Contacts
Omi is an MCP server published by BasedHardware. Marketplaces we read that list it: 1 (Docker MCP Catalog). Google Contacts is an MCP server published by domdomegg. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:674097f43757 Forks (GitHub): 2 644 Pulls (Docker Hub): 33 893 Stars (Docker Hub): 1 Stars (GitHub): 13 784 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.0 Downloads/month (npm): 441 Downloads/week (npm): 228 Forks (GitHub): 2 Stars (GitHub): 5 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 | Omi | Google Contacts |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 13 784 (better) | 5 (worse) |
| Pulls (Docker Hub) (differs) | 33 893 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 2 644 (better) | 2 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/omi) | On your machine (google-contacts-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/basedhardware/omi | github.com/domdomegg/google-contacts-mcp |
| Changes in the last 7 days | 0 | 0 |
| 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
Omi
A Model Context Protocol server for Omi interaction and automation. This server provides tools to read, search, and manipulate Memories and Conversations.
Google Contacts
Allow AI systems to list, search, and manage contacts via Google Contacts.
How to run each
Omi As a local MCP server: Docker image
claude mcp add --env "OMI_API_KEY=<YOUR_OMI_API_KEY>" --transport stdio omi -- docker run -i --rm -e OMI_API_KEY mcp/omi
Requires: OMI_API_KEY (secret)
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-mcp
Requires: GOOGLE_ACCESS_TOKEN (secret), GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), MCP_TRANSPORT
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Google Contacts publish no list of tools, so we do not compare tools.
Settings each asks for
Only Omi asks for
OMI_API_KEY (secret)
Only Google Contacts asks for
GOOGLE_ACCESS_TOKEN (secret)GOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRET (secret)MCP_TRANSPORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Omi · What it can do: Google Contacts · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.