@cocal/google-calendar-mcp vs Google Calendar MCP
@cocal/google-calendar-mcp is an MCP server published by @cocal. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Google Calendar MCP is an MCP server published by A1-x-Tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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 MCP | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 2.8.1 Downloads/month (npm): 36 840 Downloads/week (npm): 9 959 Forks (GitHub): 336 Stars (GitHub): 1 206 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 428 Downloads/week (npm): 36 Forks (GitHub): 0 Stars (GitHub): 0 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 | @cocal/google-calendar-mcp | Google Calendar MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 206 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 336 (better) | 0 (worse) |
| Last release (differs) | 2026-10-30 | Not published |
| Where it runs (differs) | On your machine (@cocal/google-calendar-mcp) | On your machine (@a1-x-tech/mcp-google-calendar) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 8, secrets among them: 3 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/nspady/google-calendar-mcp | github.com/a1-x-tech/mcp-google-calendar |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-12 | 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
@cocal/google-calendar-mcp
Google Calendar MCP Server with extensive support for calendar management
Google Calendar MCP
MCP server for the Google Calendar API: events, recurrence, invitations, availability, calendars.
How to run each
@cocal/google-calendar-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Google Calendar MCP As a local MCP server: npm package
claude mcp add --env "GOOGLE_CALENDAR_ACCESS_TOKEN=<YOUR_GOOGLE_CALENDAR_ACCESS_TOKEN>" --env "GOOGLE_CALENDAR_CLIENT_SECRET=<YOUR_GOOGLE_CALENDAR_CLIENT_SECRET>" --env "GOOGLE_CALENDAR_REFRESH_TOKEN=<YOUR_GOOGLE_CALENDAR_REFRESH_TOKEN>" --transport stdio mcp-google-calendar -- npx -y @a1-x-tech/mcp-google-calendarRequires: GOOGLE_CALENDAR_ACCESS_TOKEN (secret), GOOGLE_CALENDAR_CLIENT_SECRET (secret), GOOGLE_CALENDAR_REFRESH_TOKEN (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
The marketplaces of @cocal/google-calendar-mcp publish no settings it asks for, so we do not compare settings.
What it can do: @cocal/google-calendar-mcp · What it can do: Google Calendar MCP · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.