Google Calendar MCP wires an agent into your scheduling. It can list upcoming events, create new ones, update existing ones, run free-busy queries across multiple calendars, and resolve time-zone math without hallucinating “Tuesday at 3pm” into the wrong continent.
What it produces: list_events (with date range filter), create_event, update_event, delete_event, freebusy (which calendars are free across X-Y times). Time zones handled rigorously — events stored in UTC, displayed in the requested zone.
Best for: scheduling automation. “Find me a 30-min slot next week with my partner that respects our ‘no-meetings before 10am’ rule.” Or “block my deep-work Mondays automatically.” Especially leveraged for solo founders who own the calendar function entirely.
Skip if: you have an EA or Calendly handles your booking. Skip if your team is on Outlook — wrong calendar API. Skip for one-off “what’s on my calendar today” — the Google Calendar mobile app is faster.
Setup gotchas: OAuth setup similar to Gmail MCP. Google Cloud Console, Calendar API, OAuth client. Required scopes: calendar.readonly minimum, calendar.events for write. Tokens stored in ~/.config/google-calendar-mcp/. Multiple calendars: by default the API returns the primary; pass calendar_id explicitly for non-primary calendars or shared team calendars.
Real-world workflow: every Sunday evening, the agent reads “next 7 days of events,” summarizes blocks (deep work, calls, ops), suggests one move to maximize uninterrupted focus blocks. Two minutes of agent time, replaces Sunday-night calendar review anxiety.
Compatible alternatives: Gmail MCP for the email side of scheduling, Notion MCP if your meeting prep lives in Notion.
Free-busy queries are the killer feature. Use them; it’s the difference between “any time” and “actually open.”