Google Calendar vs io.github.theluckystrike/appointment
Google Calendar is an MCP server published by domdomegg. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.theluckystrike/appointment is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 Calendar |  io.github.theluckystrike/appointment |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.3 Downloads/month (npm): 426 Downloads/week (npm): 110 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.22.6 Forks (GitHub): 3 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
| Fact | Google Calendar | io.github.theluckystrike/appointment |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 2 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release (differs) | Not published | 2026-11-02 |
| Where it runs (differs) | On your machine (google-cal-mcp) | Remote server or your machine |
| Transport (differs) | stdio | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/domdomegg/google-calendar-mcp | github.com/theluckystrike/mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 38 h ago returned HTTP 200 |
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 Calendar
Allow AI systems to list, create, update, and manage Google Calendar events.
io.github.theluckystrike/appointment
Read your .ics calendar for appointments, free-busy windows and conflicts.
How to run each
Google Calendar 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-cal-mcp -- npx -y google-cal-mcpRequires: GOOGLE_ACCESS_TOKEN (secret), GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), MCP_TRANSPORT
io.github.theluckystrike/appointment As a remote MCP server
claude mcp add --transport http calendar-ics-reader-events-freebusy-conf https://mcp.zovo.one/mcp/calendarRequires: MCP_LICENSE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.theluckystrike/appointment has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of Google Calendar nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Only Google Calendar asks for
GOOGLE_ACCESS_TOKEN (secret)GOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRET (secret)MCP_TRANSPORT
Only io.github.theluckystrike/appointment asks for
MCP_LICENSE_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Google Calendar · What it can do: io.github.theluckystrike/appointment · 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.