WireCat Google Calendar vs Teamup Calendar MCP by usefulapi
WireCat Google Calendar is an MCP server published by wirecat.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Teamup Calendar MCP by usefulapi is an MCP server published by usefulapi.io. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.23.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 1.25.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | WireCat Google Calendar | Teamup Calendar MCP by usefulapi |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 1 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-08 (worse) | 2026-11-11 (better) |
| Where it runs (differs) | On your machine (@wirecat/gcal-cli) | Remote server (teamup-calendar.usefulapi.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/wirecatlabs/gcal-cli | github.com/m190/usefulapi-mcp |
| Changes in the last 7 days (differs) | 3 | 11 |
| First seen (differs) | 2026-11-01 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 15 h ago, requires authentication |
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
WireCat Google Calendar
Your Google Calendar for agents: sync, search and change events. Sign in with the gcal CLI first.
Teamup Calendar MCP by usefulapi
Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.
How to run each
WireCat Google Calendar As a local MCP server: npm package
claude mcp add --transport stdio gcal-cli -- npx -y @wirecat/gcal-cli mcp serve --profiles all
Teamup Calendar MCP by usefulapi As a remote MCP server
claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Teamup Calendar MCP by usefulapi 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
Neither one's marketplaces publish the settings it asks for.
What it can do: WireCat Google Calendar · What it can do: Teamup Calendar MCP by usefulapi · 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.