calendarFree

Google Calendar

Read and write a Google Calendar on behalf of an agent — book meetings, reschedule, decline, surface conflicts, and respect the operational rules that a calendar widget can't encode.

What it does

The Google Calendar MCP gives an agent the ability to manage a calendar the way a real scheduler does: not just "find a free slot" but "find a slot that respects who handles what, when this person prefers to take calls, and what the actual prep time is for this kind of meeting."

Capabilities

  • List events across one or more calendars
  • Create, update, and cancel events
  • Detect conflicts and propose alternatives
  • Respect operational rules (prep time, buffer time, blackout windows, who handles what)
  • Send invites and process responses

Operational rules

The MCP supports an operational rule set configured during onboarding:

  • Per-attendee preferences (morning person, afternoons only, no Mondays, etc.)
  • Per-meeting-type prep and buffer time
  • Blackout windows (heads-down blocks, recovery days, travel)
  • Who handles which kind of meeting (the partner handles intake, the associate handles updates, etc.)

These rules are what separate this from a generic "book a meeting" integration.

Auth

Google OAuth, scoped to calendar.events. Read-only or read-write depending on the deployment.

When to use it

  • Onyx deployments at any business that runs on Google Workspace
  • Pynk personal deployments for personal calendar management

Limitations

Calendar-only. For inbox or document interactions, pair with the Gmail or Google Drive MCPs.