Google Calendar

Google Calendar

This connector reads and manages the signed-in user's Google Calendar through the Google Calendar API v3 (https://www.googleapis.com/calendar/v3): calendars, events (list, search, read, create, change, delete), invitations, Google Meet links, quick add and free/busy. It works with personal Google accounts and Google Workspace. Everything runs as the Google account that authorized the connector.

Setup (one-time, about 10 minutes)

1. Open https://console.cloud.google.com, pick or create a project, then APIs & Services → Library → enable Google Calendar API.
2. APIs & Services → OAuth consent screen: choose Internal if you are on Google Workspace (simplest), otherwise External. For External, set the publishing status to In production: while an app is in Testing, Google revokes its refresh tokens after 7 days and the connector stops working every week. For your own use, the "unverified app" warning can be clicked through.
3. APIs & Services → Credentials → Create credentials → OAuth client ID → application type Web application → add the authorized redirect URI <your AnythingMCP URL>/api/mcp-oauth/callback (on AnythingMCP Cloud: https://cloud.anythingmcp.com/api/mcp-oauth/callback).
4. Paste the client ID and secret into GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET and install the connector.
5. On the connector page, click Authorize with Provider and sign in with the Google account whose calendars the AI should use. The refresh token is stored encrypted and access tokens are renewed automatically.

One Google client for all Google connectors: the same Cloud project and OAuth client can serve every Google connector (Gmail, Google Calendar, Google Drive, Google Sheets, Google Docs, Google Tasks, Search Console, Analytics, Ads). Enable each API in that project, reuse the same GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, and authorize each connector once: each one asks only for its own scopes.

Scope: the connector asks for https://www.googleapis.com/auth/calendar.events (create, change and delete events on every calendar the user can edit) and https://www.googleapis.com/auth/calendar.readonly (read the calendar list, calendars, colors and free/busy). It cannot create or delete calendars or change their sharing. For a read-only setup, change the scopes to https://www.googleapis.com/auth/calendar.readonly in the connector's OAuth settings, authorize again, and disable gcal_create_event, gcal_update_event, gcal_respond_to_event and gcal_quick_add.

Switched off at install: gcal_delete_event. Turn it on per tool if the AI should delete events.

Ids: calendar_id is primary for the user's main calendar; other calendars' ids come from gcal_list_calendars (an email address, or [email protected]). Event ids come from gcal_list_events. With single_events true each occurrence of a recurring event has its own id (<series id>_20261009T070000Z) and recurringEventId points to the series: change or delete the occurrence id for one date, the series id for all.

Times: RFC 3339 with an offset, e.g. 2026-10-09T09:00:00+02:00 or ...Z. start and end are objects: {"dateTime": "2026-10-09T09:00:00+02:00", "timeZone": "Europe/Berlin"} for a timed event (the time zone is required for recurring events), {"date": "2026-10-09"} for an all-day event, whose end date is exclusive (a one-day event on 9 October ends on 2026-10-10). Check the calendar's time zone with gcal_get_calendar when the user gives local times.

Listing and searching: gcal_list_events reads one calendar between time_min (compared with each event's end) and time_max (compared with its start). By default recurring events are expanded into occurrences and sorted by start time (single_events true, order_by startTime); order_by startTime is refused when single_events is false. q searches the title, description, location, guests and organizer. For "what is on my agenda" use time_min = now and a time_max a few days later.

Writing events

• gcal_create_event needs start and end; summary is the title. Guests are [{"email": "[email protected]"}], with "optional": true for optional guests.
• Guests receive an email only when send_updates is all (or externalOnly for guests outside Google Calendar). Without it nobody is notified, the event still appears in their calendars.
• Google Meet: pass conference_data {"createRequest": {"requestId": "<any unique string>", "conferenceSolutionKey": {"type": "hangoutsMeet"}}} on create or update (the connector always sends conferenceDataVersion=1). The link is returned in hangoutLink; if conferenceData.createRequest.status.statusCode is pending, read the event again a moment later.
• gcal_update_event changes only the fields given. Lists replace the whole current value: to add a guest, read the event, append to its attendees and send the full list.
• gcal_quick_add turns a sentence into an event ("Dentist Tuesday 3pm"); Google parses it, English works best. Check the returned start and end.

Responding to an invitation: read the event with gcal_get_event, change responseStatus (accepted, declined, tentative) on the attendee with "self": true and pass the whole attendees list to gcal_respond_to_event; add send_updates: "all" so the organizer gets the answer by email.

Free/busy: gcal_query_free_busy with items: [{"id": "primary"}, {"id": "[email protected]"}] returns busy intervals only. Colleagues' calendars answer only when their free/busy is visible to the user (usually inside the same Workspace organisation); otherwise the calendar carries an errors entry such as notFound.

Pagination: list responses carry nextPageToken while more results exist; call the same tool with the same arguments and page_token set to it. max_results goes up to 2500 events (250 calendars).

Quotas: the Calendar API meters requests per minute per project and per user. Over the limit Google answers 403 rateLimitExceeded / userRateLimitExceeded or 429: wait a little and retry, and avoid tight loops of single-event calls.

Common errors

• 401: the authorization expired or was revoked (always after 7 days while the consent screen is in Testing). Click Authorize with Provider again.
• 403 insufficientPermissions: the scope does not allow the call (a write on a read-only setup), or the user has only read access to that calendar. 403 accessNotConfigured: enable the Google Calendar API in the Cloud project.
• 404: the calendar or event id does not exist or is not visible to this account. 410: the event was deleted.
• 400 timeRangeEmpty or Bad Request: a start after the end, a missing offset in a date-time, or order_by startTime without single_events.

Out of scope here: creating, deleting or sharing calendars, event attachments, settings and push notifications.