Google Calendar MCP.
Run your own server, or connect one URL.
A Google Calendar MCP server lets Claude, Codex, Cursor, and other AI agents read your schedule and act on it — create events, invite people, RSVP. Here's the honest version of both routes: the self-hosted setup, step by step, and the hosted one that takes a minute.
Option 1: Self-hosted, step by step
The open-source route gives you full control and keeps credentials on your machine. It requires a Google Cloud project and about twenty minutes the first time. Google also offers an official remote Calendar MCP server for Workspace developers — same Google Cloud prerequisites apply.
- 1Create a Google Cloud projectSign in to the Google Cloud console, create a project, and enable the Google Calendar API under APIs & Services.
- 2Configure the OAuth consent screenSet up the consent screen, add the calendar scopes, and add your own Google account as a test user.
- 3Create OAuth credentialsCreate an OAuth 2.0 Client ID (Desktop type) and download the credentials JSON file to your machine.
- 4Install and run a serverPick an open-source implementation — nspady/google-calendar-mcp on GitHub is the most established — point it at your credentials file, and run it locally.
- 5Add it to your client and authorizeRegister the server in Claude Desktop's config file or via the Claude Code CLI, restart, and complete the Google authorization in your browser.
- 6Re-authorize weekly (testing mode)While your consent screen is in testing mode, Google expires tokens after 7 days. Publish the app — with Google's verification process — to make sign-in stick.
Option 2: Hosted, two steps
The hosted route runs through Amie — an Amie account is what holds the Google connection your agent talks to. In exchange: no Google Cloud console, no credentials file, no weekly re-authorization, and todos plus meeting notes come through the same connection.
- 1Get Amie and connect Google CalendarSign up for Amie and connect your Google account — calendars sync right away, and you can connect work and personal accounts side by side.
- 2Add the server to your agentPaste this URL into your MCP client (in Claude: Settings → Connectors → Add custom connector) and approve the sign-in prompt.
https://mcp.amie.so
That's the whole setup. Client-specific instructions — Claude Code, Codex, Cursor — plus the full tool list and permissions are on the Amie MCP server page.
What it unlocks
The agent checks real availability, resolves names to actual contacts, and controls whether attendees get emailed — the difference between a calendar integration and a calendar that works for you.