Best Google Calendar MCP Servers in 2026

We dug through every Google Calendar MCP server we could find in 2026, ranked them honestly, and noted who each one is for. Yes, we run one of them. Yes, we will tell you when a competitor is the better choice.

This list is current as of April 2026. The MCP ecosystem moves fast, so check the upstream repos before committing.

The shortlist

1. CalendarMCP — hosted, deepest tooling, GAP-friendly
2. nspady/google-calendar-mcp — the popular open-source self-hosted option
3. Composio Calendar — calendar inside a multi-tool platform
4. Zapier MCP (calendar actions) — familiar Zapier surface, MCP wrapper
5. Pipedream Connect (calendar) — similar idea, different host
6. Roll your own — thinnest path if you have one specific use case

1. CalendarMCP

What it is: A hosted Google Calendar MCP server. Connect Google in two clicks, get an API key, plug it into Claude.ai, Claude Code, Cursor, or any HTTP-capable MCP client.

Why we list it first: Because we built it. We will let the feature list defend the position.

• Ten calendar tools covering reads, writes, batch updates, and free-time search.
• One API key spans many Google accounts (mix OAuth and service accounts).
• Per-calendar read/write matrix so an agent can never touch the wrong calendar.
• Service account flow that works with Google Advanced Protection.
• Native HTTP MCP transport, works with every MCP client we have tested.
• Free tier covers individual users.

Best for: Anyone who wants calendar tools working in 2 minutes, and anyone whose agent does enough calendar work that batch operations and multi-calendar support actually matter.

Avoid if: You are firmly in the self-host camp and would rather hold your own OAuth tokens.

2. nspady/google-calendar-mcp

What it is: The most popular open-source self-hosted Google Calendar MCP server, with over a thousand GitHub stars. Stdio MCP, runs locally, BYO Google OAuth credentials.

• Open source, you can read or fork the code.
• Free, no rate limits beyond Google's.
• Tokens never leave your machine.
• Solid baseline calendar tools.

Trade-offs: Setup takes 25 to 40 minutes. Stdio MCP only, so no Claude.ai or Claude Code support without a wrapper. No batch operations, no multi-calendar fan-out, no multi-account-per-key. OAuth tokens expire every 7 days unless you verify your consent screen with Google. Cannot work around Google Advanced Protection.

Best for: Privacy-focused users on Claude Desktop who are happy with the setup overhead.

3. Composio Calendar

What it is: Calendar tools as part of Composio's broader tool platform. Connect Google Calendar through Composio's auth flow, get a unified runtime that also covers Slack, Notion, Linear, Gmail, and dozens more.

• Best fit if your agent uses many tools across many services.
• Single auth model and billing relationship.
• Calendar surface covers the basics: list, create, update, delete, find free time.

Trade-offs: Calendar tools are shallower than a calendar-specific service. No deep batch operations. No service-account flow for Google Advanced Protection. Pricing is geared toward teams running many actions across many tools, which can be overkill for calendar-only agents.

Best for: Multi-service agents where calendar is one node among ten.

4. Zapier MCP (calendar actions)

What it is: Zapier exposed an MCP wrapper over their existing calendar actions in late 2025. You connect Zapier to Google Calendar like any Zap, then expose those actions to your AI client through MCP.

• Familiar surface if you already use Zapier.
• Reuses your existing Zap connections.
• Good fit when calendar work is glued into other Zapier-powered automation.

Trade-offs: Zapier's calendar actions are CRUD-shaped, not calendar-shaped. Recurring events, batch operations, and multi-calendar fan-out are second-class. Pricing per task adds up if your agent is chatty.

Best for: Teams already paying for Zapier who want a quick MCP bridge to existing automations.

5. Pipedream Connect (calendar)

What it is: Pipedream's analogue of the Zapier story. Connected accounts, scripted workflows, and an MCP layer over the top.

• More flexible than Zapier (you can write JS).
• Free tier is generous for low-volume use.
• Works well if your agent is part of a larger Pipedream workflow.

Trade-offs: Same as Zapier: calendar tools are CRUD, depth is limited, and you are paying for an automation platform whose calendar piece is a feature, not the product.

Best for: Pipedream users who want to bridge an agent into existing scripted workflows.

6. Roll your own

What it is: A 50 line Python or Node script wrapping the Google Calendar API and exposing it as an MCP server.

• Cheapest option if you already know what you need and it is small.
• Total control.
• Useful as a learning project.

Trade-offs: You are the maintainer now. OAuth, retries, error handling, schema definitions, recurrence edge cases, batch endpoints, timezone math — all yours. The MCP world is full of half-finished side projects that started as "I'll just write 50 lines".

Best for: Hackers and people who specifically want to learn the surface.

Decision matrix

What we expect to change in 2026

• More HTTP MCP servers will arrive. Stdio-only is becoming the minority position.
• Service account flows will become standard for any product serving security-conscious users.
• Batch endpoints will become table stakes once people realise N round trips do not scale.
• Zapier and Pipedream will close some of the calendar depth gap, but probably not all of it.

We will refresh this post when the lineup shifts. If you run a calendar MCP server we missed, send a note and we will look at it.