Ext Ops Panel
Open dashboard
Comparison

Omi vs WireCat Google Calendar

Omi is an MCP server published by BasedHardware. Marketplaces we read that list it: 1 (Docker MCP Catalog). WireCat Google Calendar is an MCP server published by wirecat.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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

Where each is published
MarketplaceOmiWireCat Google Calendar
Docker MCP Catalog Listed
Version: sha256:674097f43757
Forks (GitHub): 2 700
Pulls (Docker Hub): 34 407
Stars (Docker Hub): 1
Stars (GitHub): 13 955
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.23.0
Forks (GitHub): 0
Stars (GitHub): 2
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

Omi vs WireCat Google Calendar
FactOmiWireCat Google Calendar
Marketplaces that list it11
Stars (GitHub) (differs)13 955 (better)2 (worse)
Pulls (Docker Hub) (differs)34 407No figure on Docker Hub
Forks (GitHub) (differs)2 700 (better)0 (worse)
Last release (differs)Not published2026-11-08
Where it runs (differs)On your machine (mcp/omi)On your machine (@wirecat/gcal-cli)
Transportstdiostdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/basedhardware/omigithub.com/wirecatlabs/gcal-cli
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-11-01

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

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for Omi interaction and automation. This server provides tools to read, search, and manipulate Memories and Conversations.

WireCat Google Calendar

In its own words, on Official MCP Registry:

Your Google Calendar for agents: sync, search and change events. Sign in with the gcal CLI first.

How to run each

Omi As a local MCP server: Docker image

Claude Code
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)

WireCat Google Calendar As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio gcal-cli -- npx -y @wirecat/gcal-cli mcp serve --profiles all

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of WireCat Google Calendar publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of WireCat Google Calendar publish no settings it asks for, so we do not compare settings.

What it can do: Omi · What it can do: WireCat Google Calendar · 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.

Where the data comes from: how the catalog is built