Ranked roundup · Google Calendar
Best MCP Server for Google Calendar
There is now an official MCP server for Google Calendar, which changes the usual calculus for this category. Google runs a remote server at calendarmcp.googleapis.com as part of the Workspace Developer Preview Program - real first-party support, OAuth 2.0, event and availability tools - but it is a preview, requires program enrollment, and still needs your own Google Cloud project and OAuth client. The community got there first and stayed practical: nspady's dedicated calendar server (1,179 GitHub stars) and taylorwilsdon's broader Workspace server (3,098 stars, pushed within days of our check) both cover event CRUD, free/busy, and recurring events, both MIT-licensed. Managed platforms - Composio and Zapier - remove the Google Cloud Console step entirely by hosting the OAuth connection for you. We ranked all five on verifiable criteria: official status, maintenance recency, adoption, auth model, and documented capability coverage, checked against GitHub and vendor docs on September 1, 2026. Nobody paid for placement. The real pain in this category is OAuth setup, and the ranking weighs who reduces it without hiding the cost.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Official · Google
Anyone who wants first-party support and a Google-hosted endpoint, and can live with preview-stage software
Eight tools per the API reference: create_event, update_event, delete_event, get_event, list_events, list_calendars, respond_to_event, and suggest_time - event CRUD, availability checking, and RSVP responses
Remote server hosted by Google at calendarmcp.googleapis.com/mcp/v1 - no local process to run · OAuth 2.0. You create a client ID and secret in your own Google Cloud project, configure the consent screen and scopes, and authenticate through your MCP client
- Developer Preview only - requires enrollment in the Google Workspace Developer Preview Program, and behavior or terms can change before general availability
- The hosted endpoint does not remove setup work: you still need a Google Cloud project with the Calendar API and Calendar MCP API enabled, plus your own OAuth client and consent screen
- Google's own docs warn the server can read, modify, and delete data in your Google Account and flag indirect prompt-injection risk - do not point it at untrusted content
- Community
The deepest Google Calendar-specific coverage in a self-hosted server you can run today
Event CRUD, multi-calendar and multi-account queries, cross-calendar conflict detection, free/busy availability, recurring event handling, accept/decline/tentative responses, event extraction from images, PDFs, and web links, tool filtering to trim context
Self-hosted - npm package @cocal/google-calendar-mcp via npx, local install, or Docker; stdio by default with an HTTP mode · OAuth 2.0 Desktop-app credentials JSON from your own Google Cloud project, passed via GOOGLE_OAUTH_CREDENTIALS; tokens persist locally · MIT · 1,179★
- Unofficial - no Google affiliation or support
- OAuth apps left in test mode expire tokens every 7 days, forcing re-authentication; the fix is publishing your OAuth app to production mode
- You must add your own email as a test user on the consent screen before the auth flow works at all
- No pushes since June 1, 2026 as of our September 1 check - about three months quiet, though not archived
- Community
Running Calendar plus the rest of Google Workspace behind a single MCP server - and it is the most actively maintained option here (pushed 2 days before our check)
Seven Calendar tools covering events, free/busy, Out of Office, and Focus Time - alongside Gmail, Drive, Docs, Sheets, Slides, Chat, Forms, and Tasks in one server, with core/extended/complete tool tiers
Self-hosted Python - uvx workspace-mcp --tools calendar from PyPI, or Docker; stdio or streamable HTTP transport · OAuth 2.0 client credentials from your Cloud project; optional OAuth 2.1 PKCE mode for multi-user deployments over HTTP; service accounts with domain-wide delegation for Workspace admins · MIT · 3,098★
- Unofficial - no Google affiliation or support
- Calendar is one module of nine-plus; without the --tools calendar filter you carry a much larger tool and scope surface than a calendar-only server
- Still requires your own Google Cloud project, enabled APIs, and OAuth client - the auth setup pain is not removed, just well documented
- Community
Skipping Google Cloud Console entirely - the fastest path from zero to a working calendar connection
Event creation and scheduling, event listing and filtering, calendar creation and management, per its toolkit docs; a tool-router mode loads Calendar tools alongside other apps through one endpoint
Fully managed - Composio hosts the MCP endpoint and the Google connection; nothing to run locally · Composio-hosted OAuth flow - no Google Cloud project needed to start; you can optionally bring your own OAuth credentials and restrict which scopes and actions are allowed
- A third party sits in the data path between your agent and your calendar
- Free tier is capped at 20,000 tool calls per month per Composio's site; beyond that you are on paid plans
- Not open source - you depend on Composio's uptime, pricing, and terms
- Community
Teams already on Zapier who want calendar actions exposed to an AI client without any new infrastructure
Roughly 20 Google Calendar operations per its listing: 8 write actions (create/update/delete events, quick-add from text, manage attendees, move events between calendars), 5 search actions, 7 triggers, plus find-or-create
Fully managed remote server hosted by Zapier · Zapier-hosted Google OAuth connection - you authorize once in Zapier's UI, no Cloud project required
- A third party sits in the data path between your agent and your calendar
- Search actions cap at 250 returned events or calendars
- The Google Calendar MCP page does not publish usage limits - check your Zapier MCP plan's tool-call allowance before relying on it
- Tools mirror Zapier's action shapes rather than the raw Calendar API, so fine-grained control is narrower than self-hosted options
Google Calendar MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Google Calendar MCP server (official) | Remote server hosted by Google at calendarmcp.googleapis.com/mcp/v1 - no local process to run | OAuth 2.0. You create a client ID and secret in your own Google Cloud project, configure the consent screen and scopes, and authenticate through your MCP client | — | |
| nspady/google-calendar-mcp | Community | Self-hosted - npm package @cocal/google-calendar-mcp via npx, local install, or Docker; stdio by default with an HTTP mode | OAuth 2.0 Desktop-app credentials JSON from your own Google Cloud project, passed via GOOGLE_OAUTH_CREDENTIALS; tokens persist locally | MIT |
| taylorwilsdon/google_workspace_mcp | Community | Self-hosted Python - uvx workspace-mcp --tools calendar from PyPI, or Docker; stdio or streamable HTTP transport | OAuth 2.0 client credentials from your Cloud project; optional OAuth 2.1 PKCE mode for multi-user deployments over HTTP; service accounts with domain-wide delegation for Workspace admins | MIT |
| Composio (Google Calendar toolkit) | Community | Fully managed - Composio hosts the MCP endpoint and the Google connection; nothing to run locally | Composio-hosted OAuth flow - no Google Cloud project needed to start; you can optionally bring your own OAuth credentials and restrict which scopes and actions are allowed | — |
| Zapier MCP (Google Calendar) | Community | Fully managed remote server hosted by Zapier | Zapier-hosted Google OAuth connection - you authorize once in Zapier's UI, no Cloud project required | — |
How to choose
Pick Google's official server if you want vendor support and can accept Developer Preview status - you enroll in the program, bring your own OAuth client, and get first-party tools on a Google-hosted endpoint. Pick nspady/google-calendar-mcp if you want the deepest calendar-specific coverage that works today: multi-account queries, conflict detection, free/busy. Pick taylorwilsdon/google_workspace_mcp if Calendar is one of several Workspace apps you need - it is the most actively maintained of the group. Pick Composio or Zapier if you refuse to touch Google Cloud Console: they host the OAuth flow for you, at the cost of putting a third party in your calendar's data path.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Is there an official Google Calendar MCP server?
- Yes. Google runs a remote MCP server at calendarmcp.googleapis.com/mcp/v1 with eight tools covering event CRUD, availability, and RSVPs. It is in Developer Preview - you must enroll in the Google Workspace Developer Preview Program and still set up your own Google Cloud project and OAuth client.
- Why is OAuth setup the hard part for Google Calendar MCP servers?
- Every self-hosted option - including Google's own - requires a Google Cloud project, the Calendar API enabled, an OAuth client, and a configured consent screen. On nspady's server, an OAuth app left in test mode also expires its tokens every 7 days until you publish it to production. Composio and Zapier exist largely because they host this flow for you.
- Can an MCP server delete my calendar events?
- Yes - delete_event is a standard tool on the official server and most community ones, and Google's docs explicitly warn that an MCP host can read, modify, and delete account data. Use scope restriction where offered (taylorwilsdon's server and Composio both support it) and keep untrusted content away from an agent holding calendar write access.
- Should I use a Calendar-only server or a full Google Workspace server?
- Calendar-only (nspady) gives deeper calendar features like cross-calendar conflict detection and multi-account queries with a smaller permission surface. The Workspace server (taylorwilsdon, 3,098 stars, pushed August 30, 2026) makes sense when you also need Gmail, Drive, or Docs - and it can be filtered down to calendar tools only.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.