Updated ranking of every Google Calendar MCP server in May 2026. Includes nspady, Composio, Zapier, Coupler, FlowHunt, calendarapi-mcp, Nextcloud, MEOK, and Apple Calendar options.
The first version of this roundup ran in April 2026. A lot has changed. More servers exist, some have improved substantially, and the hosted vs self-hosted split has sharpened. This is the updated list for May 2026. We run one of these. We will still tell you when another is the better pick.
Every Google Calendar MCP server we could verify as working in May 2026, in honest rank order:
Type: Open source, self-hosted, stdio MCP.
Still the most popular Google Calendar MCP project on GitHub, now well past a thousand stars. The code is clean, the tool coverage is solid for basic CRUD, and the community has contributed fixes and improvements throughout Q1 2026.
Best for:Privacy-conscious users on Claude Desktop who want zero third parties in the chain. Setup takes 25 to 40 minutes, tokens stay on your machine, and it is free with no rate limits beyond Google's own.
Limitations: Stdio transport only, so Claude.ai, Claude Code, and Cursor do not work without a wrapper. Single Google account per token. No batch operations. OAuth tokens expire every 7 days if you do not verify your consent screen with Google (which takes 1 to 6 weeks). Does not work with Google Advanced Protection.
Type: Hosted, HTTP MCP transport.
We built this one, so take the placement with appropriate skepticism. The reason it is ranked second rather than first is that nspady genuinely wins on the axes that matter most to privacy-focused self-hosters.
CalendarMCP's case rests on the feature set: ten calendar tools including batch operations and multi-calendar fan-out, one API key spanning multiple Google accounts, per-calendar read/write scope control, a service account flow that works with Google Advanced Protection, and HTTP MCP transport that supports Claude.ai, Claude Code, Cursor, OpenClaw, and anything else that speaks HTTP MCP.
Best for: Anyone using Claude.ai, Claude Code, Cursor, or a gateway-based agent. Anyone managing more than one Google account. Anyone building a calendar-heavy agent where batch operations matter.
Worst pick if: You need offline-only operation, or your threat model requires that no third party ever touches your calendar tokens.
Type: Hosted, part of a multi-tool platform.
Calendar tools as one node in Composio's broader tool graph. If your agent already uses Composio for Slack, Gmail, Notion, and Linear, adding calendar there keeps everything in one auth and billing relationship. The calendar surface covers the basics well.
Best for: Multi-tool agents where calendar is one capability among many.
Limitations: Calendar depth is shallower than a calendar-specific service. No batch operations, no service account flow for GAP, and pricing is shaped around teams running many actions across many services.
Type:Hosted, MCP wrapper over Zapier's calendar actions.
Zapier exposed MCP access to their calendar actions in late 2025. If you are a Zapier user with existing Google Calendar connections, this is the path of least resistance. The tools are CRUD-shaped rather than calendar-native, and per-task pricing adds up for chatty agents.
Best for: Teams already paying for Zapier who want a quick MCP bridge to existing automations.
Type:Hosted, part of Coupler's data connector platform.
Coupler is primarily a reporting and data pipeline tool. Their MCP calendar connector leans toward read-heavy use cases: pulling calendar data into reports, dashboards, and data workflows. Not the right pick for an agent that needs to create and modify events frequently.
Best for: Analytics-oriented agents that need to read calendar data alongside other data sources.
Type: Hosted, part of the FlowHunt no-code agent platform.
FlowHunt's MCP server gives their platform users calendar access as part of agent flows. The tool surface is narrower than dedicated calendar servers, and the product is primarily aimed at FlowHunt platform users rather than developers configuring their own clients.
Best for: FlowHunt users who want to add calendar context to existing flows.
Type: Open source, self-hosted, focused on the CalDAV standard.
A lighter-weight open-source option compared to nspady. Targets CalDAV rather than the Google Calendar API specifically, which means it works with non-Google CalDAV servers (Nextcloud, Fastmail, Apple Calendar Server) as well as Google. Narrower tool coverage.
Best for: Developers who need a CalDAV-compatible MCP server, especially for non-Google calendar backends.
Type: Open source, self-hosted, Nextcloud-specific.
Exactly what it sounds like: an MCP server for Nextcloud Calendar. If you self-host Nextcloud as your calendar backend this is the obvious choice. Completely irrelevant if you use Google Calendar.
Best for: Nextcloud users.
Type: Hosted consumer product with MCP access.
MEOK is a consumer-facing calendar AI assistant that added MCP integration. The product is more polished on the UI side than most MCP servers, and less focused on developer configurability. Not a natural fit for agent-native workflows where you want to control tool selection and prompting.
Best for: Non-technical users who want a chat interface around their calendar and do not need fine-grained MCP control.
Type: Open source, self-hosted, Apple Calendar (not Google).
Listed here because people searching for a calendar MCP on macOS sometimes want Apple Calendar, not Google Calendar. supermemoryai's apple-mcp project covers the Apple Calendar, Reminders, and Contacts APIs via EventKit. Works locally on macOS through Calendar app, including Google Calendar and Exchange accounts synced to Apple Calendar.
Best for: macOS users who sync all their calendars through Apple Calendar and want a local tool that reads all of them at once via EventKit.
We will update this list when the lineup shifts. If we missed a server, contact us and we will look at it.
Ready to try the hosted option? CalendarMCP connects in two minutes with no Google Cloud setup required.
Connect your Google Calendar to Claude and any MCP client in about two minutes.
Connect Google Calendar