Labsco
MCP SERVER

Google Calendar

by nspady ↗

Query several Google accounts' calendars at once — find where a week is actually free, respond to invitations, and add an event from a screenshot.

Calendars, Meetings & Scheduling
Summary
Availability across every calendar you have, answered in one question.

Most calendar integrations connect one account. Connecting work and personal together is what turns "when am I free" from a question you answer by tabbing between two browser windows into one the assistant can just answer.

What it is

A Google Calendar integration that connects more than one Google account and treats them as one searchable surface. Read-only tools merge results across accounts; write tools pick the account with the right permissions.

What you get
  • `list-calendars`, `list-events` with date filtering, `get-event` by ID and `search-events` by text query
  • `create-event`, `update-event` and `delete-event`, with advanced handling for modifying recurring events
  • `respond-to-event` for accepting, declining, marking maybe or clearing a response — including accepting one instance of a recurring meeting while leaving future ones tentative
  • `get-freebusy` to check availability across calendars, including external ones, which is what makes cross-account conflict detection work
  • `get-current-time` in the calendar's own timezone, `list-colors`, and `manage-accounts` for adding, listing and removing connected Google accounts from the chat
  • `ENABLED_TOOLS` to expose only the tools a workflow needs, cutting the token cost of the unused schemas while still telling the assistant which capabilities exist but are switched off
Requirements

A Google Cloud project with the Calendar API enabled and OAuth 2.0 credentials of the Desktop app type — the application type matters. Add your own address as a test user on the Audience screen; propagation can take a few minutes. Run it with `npx @cocal/google-calendar-mcp` and set `GOOGLE_OAUTH_CREDENTIALS` to the path of your keys file, which is mandatory on the npx path. Before any calendar tool works you must ask the assistant to authenticate; skipping that step returns a `-32600` error. While the app is in test mode tokens expire after 7 days — publishing the app to production mode removes that at the cost of an unverified-app warning. Tokens are stored in your system's config directory and credentials never leave the machine.

Setup effort

One command plus a key — npx @cocal/google-calendar-mcp, then supply credentials