--- title: "Google Calendar MCP server for AI agents - actionlake" description: "Give Claude 38 Google Calendar actions through one MCP server: events, calendarlist, acl. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/google-calendar updated: 2026-10-10 --- Connectors · Workspace # Google Calendar MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Calendar and the rest of your systems. It gives your agent 38 Google Calendar actions (12 reads, 19 writes and 7 that wait for a confirmation) and holds the Google Calendar credential itself, so the agent never does. It paces Google Calendar's limits and records every call. Connecting Google Calendar needs your own Google Calendar OAuth app and one admin sign-in. [Connect Google Calendar free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "gws_calendar.events.list", intent: "check which Google Calendar account is connected" } # List calendar events · read · 1 upstream call ``` - 38 actions in one signed file - 12 read look, never change - 19 write create and update - 7 wait for a yes destructive, confirmed first Set up ## Connect Google Calendar in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Google Calendar. OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Calendar, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key. Before the first sign-in, Google Calendar needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Calendar app to lend you. - `access_token` Access token from one sign-in with your own OAuth app - `refresh_token` Refresh token from the same sign-in; the access token is renewed from it - `client_id` Google OAuth client id - `client_secret` Google OAuth client secret ``` account { op: "connections.requirements", service: "gws_calendar" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "gws_calendar.events.list" } # list calendar events · read · 1 upstream call check { action: "gws_calendar.events.import", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Google Calendar at a glance **Sign-in** OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Calendar, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. **You provide** `access_token` `refresh_token` `client_id` `client_secret` **Limits we pace to** 600 calls a minute, per connection **API covered** Google Calendar API 3`www.googleapis.com/calendar/v3` **Built from** Google Calendar's documentation, read 8 September 2026[developers.google.com](https://developers.google.com/workspace/calendar/api/v3/reference) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 12 of 12 reads, for up to an hour; a write clears what it affects **Ready-made plans** 6 in the store **Shared entities** 2, so ask can line Google Calendar up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Google Calendar. 38 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest. - **12** read look, never change - **19** write create and update - **7** destructive wait for a confirmation 1. ### Calendar 38 12 read · 19 write · 7 destructive List calendar events · List the user's calendars · Import a calendar event · Create a calendar event Top actions ## The Google Calendar API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 25 of Google Calendar's 25 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `gws_calendar.events.list` List calendar events | List events on a calendar within a time window, optionally expanding recurrences. | read | `comm.event.list` 61 connectors | | `gws_calendar.calendar_list.list` List the user's calendars | List every calendar in the authenticated user's calendar list, with their access roles. | read | `comm.calendar.list` 14 connectors | | `gws_calendar.events.import` Import a calendar event | Import an existing event, preserving its original iCalendar UID. | write | `comm.event.create` 52 connectors | | `gws_calendar.acl.list` List a calendar's access rules | List who may see or change a calendar, and at what level. | read | `comm.calendar_permission.list` 3 connectors | | `gws_calendar.events.delete` Delete a calendar event | Remove an event from a calendar. | destructive | `comm.event.delete` 45 connectors | | `gws_calendar.calendars.insert` Create a calendar | Create a new secondary calendar owned by the authenticated user. | write | `comm.calendar.create` 11 connectors | | `gws_calendar.acl.watch` Watch a calendar's access rules | Register a webhook channel to be notified when a calendar's sharing changes. | write | `automation.webhook.create` 209 connectors | | `gws_calendar.events.watch` Watch a calendar's events | Register a webhook channel to be notified when a calendar's events change. | write | `automation.webhook.create` 209 connectors | | `gws_calendar.acl.get` Get one calendar access rule | Fetch a single sharing rule by its id. | read | `comm.calendar_permission.get` 2 connectors | | `gws_calendar.freebusy.query` Query free/busy information | Ask when a set of calendars is busy across a time window. | read | `comm.availability.query` 5 connectors | | `gws_calendar.events.instances` List a recurring event's occurrences | List the individual occurrences a recurring event expands into. | read | `comm.event_instance.list` 3 connectors | | `gws_calendar.colors.get` Get the calendar colour palette | Fetch the fixed palette of colour ids calendars and events may use. | read | `platform.picklist_value.list` 52 connectors | Try it ## Prompts to paste into Claude. Each one names the Google Calendar actions it will call, so you know what it reads and what it changes before you send it. 1. Read read What is on the Google Calendar calendar this week? calls `gws_calendar.events.list` 2. Plan destructive Cancel the remaining instances of a recurring meeting in Google Calendar. Ask me before anything is sent or changed. calls `gws_calendar.events.get` `gws_calendar.events.instances` `gws_calendar.events.patch` `gws_calendar.events.delete` `gws_calendar.events.list` 3. Plan destructive Remove a leaver's calendar access and hand over ownership in Google Calendar. Ask me before anything is sent or changed. calls `gws_calendar.calendars.get` `gws_calendar.acl.get` `gws_calendar.acl.delete` `gws_calendar.calendars.transfer_ownership` `gws_calendar.acl.list` 4. Write write Import a calendar event in Google Calendar. Show me exactly what you will send before you save it. calls `gws_calendar.events.import` The plan store ## Ready-made plans for Google Calendar. 6 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design. 1. ### Audit who a calendar is shared with Use it when Someone needs to know who currently has access to a calendar and at what level. **Effect** read **Steps** 4 · loops **Needs** calendar id and min access role **Install** `gws_calendar-audit-calendar-sharing` 2. ### Build a weekly agenda digest from the calendar Use it when Someone wants a readable rundown of what is on a calendar over a date range. **Effect** read **Steps** 4 · loops **Needs** calendar id, time max and time min **Install** `gws_calendar-weekly-agenda-digest` 3. ### Find a free slot and book a meeting Use it when A meeting needs scheduling across several people and the time must be checked before anything is sent. A person decides Book '_summary_' in the window _window_ for _attendees_. **Effect** write **Steps** 5 **Needs** attendees, location, summary, time max and time min **Install** `gws_calendar-find-slot-and-book` 4. ### Create a team calendar and share it with the team Use it when A new shared team or project calendar has to be stood up and handed to a group. A person decides Grant _role_ access on the new calendar '_summary_' to _members_, which emails them an invitation. **Effect** write **Steps** 6 · loops **Needs** color id, description, location, members, role, summary and time zone **Install** `gws_calendar-provision-team-calendar` 5. ### Cancel the remaining instances of a recurring meeting Use it when A recurring meeting should stop and the attendees must be told. A person decides Cancel the recurring event _event id_ and every occurrence from _cutoff_ onward, emailing all attendees. **Effect** destructive **Steps** 6 **Needs** calendar id, cutoff, event id, reason and time max **Install** `gws_calendar-cancel-recurring-series` 6. ### Remove a leaver's calendar access and hand over ownership Use it when Someone has left or changed role and their access to a shared calendar must be revoked. A person decides Delete access rule _rule id_ on calendar _calendar id_ and transfer ownership to _new data owner_. **Effect** destructive **Steps** 6 **Needs** calendar id, new data owner and rule id **Install** `gws_calendar-offboard-calendar-access` install a plan ``` account { op: "plans.install", slug: "gws_calendar-audit-calendar-sharing" } # then ask for it by name; a schedule can run it on a timetable ``` Governance for Google Calendar ## Destructive actions wait for a yes. 7 Google Calendar actions are destructive. These are all of them: - Delete a calendar event `gws_calendar.events.delete` - Clear a calendar `gws_calendar.calendars.clear` - Transfer a calendar's ownership `gws_calendar.calendars.transfer_ownership` - Delete a calendar `gws_calendar.calendars.delete` - Revoke access to a calendar `gws_calendar.acl.delete` - Stop a calendar notification channel `gws_calendar.channels.stop` - Unsubscribe from a calendar `gws_calendar.calendar_list.delete` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do gws_calendar.events.delete confirm_policy: **human** Delete a calendar event? **intent:** the user asked me to delete a calendar event run suspended · waiting for a named person · key _gws-calendar-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "gws-calendar-agent", allowed_actions: ["gws_calendar.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "gws_calendar.events.delete", approver: "lead@example.com" }, { match: "gws_calendar.calendars.clear", approver: "lead@example.com" }, { match: "gws_calendar.calendars.transfer_ownership", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Google Calendar only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Google Calendar costs on actionlake. Every Google Calendar action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Google Calendar refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 38 Google Calendar actions - 7 actions page each page of a long list is one call - 12 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Google Calendar action. 38 actions by area: the id your agent calls, what it does, and its effect. **Calendar 38** - `gws_calendar.acl.delete` Revoke access to a calendar destructive - `gws_calendar.acl.get` Get one calendar access rule read - `gws_calendar.acl.insert` Grant access to a calendar write - `gws_calendar.acl.list` List a calendar's access rules read - `gws_calendar.acl.patch` Patch a calendar access rule write - `gws_calendar.acl.update` Replace a calendar access rule write - `gws_calendar.acl.watch` Watch a calendar's access rules write - `gws_calendar.calendar_list.delete` Unsubscribe from a calendar destructive - `gws_calendar.calendar_list.get` Get one calendar list entry read - `gws_calendar.calendar_list.insert` Subscribe to a calendar write - `gws_calendar.calendar_list.list` List the user's calendars read - `gws_calendar.calendar_list.patch` Patch a calendar list entry write - `gws_calendar.calendar_list.update` Replace a calendar list entry write - `gws_calendar.calendar_list.watch` Watch the user's calendar list write - `gws_calendar.calendars.clear` Clear a calendar destructive - `gws_calendar.calendars.delete` Delete a calendar destructive - `gws_calendar.calendars.get` Get a calendar read - `gws_calendar.calendars.insert` Create a calendar write - `gws_calendar.calendars.patch` Patch a calendar write - `gws_calendar.calendars.transfer_ownership` Transfer a calendar's ownership destructive - `gws_calendar.calendars.update` Replace a calendar write - `gws_calendar.channels.stop` Stop a calendar notification channel destructive - `gws_calendar.colors.get` Get the calendar colour palette read - `gws_calendar.events.delete` Delete a calendar event destructive - `gws_calendar.events.get` Get one calendar event read - `gws_calendar.events.import` Import a calendar event write - `gws_calendar.events.insert` Create a calendar event write - `gws_calendar.events.instances` List a recurring event's occurrences read - `gws_calendar.events.list` List calendar events read - `gws_calendar.events.move` Move a calendar event to another calendar write - `gws_calendar.events.patch` Patch a calendar event write - `gws_calendar.events.quick_add` Quick-add a calendar event from text write - `gws_calendar.events.update` Replace a calendar event write - `gws_calendar.events.watch` Watch a calendar's events write - `gws_calendar.freebusy.query` Query free/busy information read - `gws_calendar.settings.get` Get one calendar preference read - `gws_calendar.settings.list` List calendar preferences read - `gws_calendar.settings.watch` Watch calendar preferences write Questions ## The Google Calendar MCP server, answered. **Is there a Google Calendar MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 38 Google Calendar actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Calendar. **What do I need to connect Google Calendar?** Your own Google Calendar OAuth app, registered with Google Calendar (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Calendar app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "gws_calendar" } lists exactly what to paste. **Can an AI agent delete or change things in Google Calendar?** Only if its key allows it, and only with an explicit confirmation. 7 Google Calendar actions are destructive, including delete a calendar event, clear a calendar and transfer a calendar's ownership. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Google Calendar API limit?** actionlake paces every call to the limits in the Google Calendar service file: 600 calls a minute per connection. Repeated reads are answered from cache (12 Google Calendar actions can be), which never reaches Google Calendar. **What does a Google Calendar action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (7 Google Calendar actions page). Cache hits, searches, dry runs and calls Google Calendar refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Google Calendar API does it cover?** The Google Calendar API 3 at www.googleapis.com/calendar/v3. It is built from Google Calendar's documentation as read on 8 September 2026. 38 actions in 1 area, each one in the signed service file (version 1.0.0). **Does actionlake keep my Google Calendar data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Calendar credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Google Calendar Shares the most action names with - [Microsoft 365 Calendar 18](https://actionlake.com/connectors/microsoft-365-calendar) - [Recall.ai 7](https://actionlake.com/connectors/recall-ai) - [Google Forms 2](https://actionlake.com/connectors/google-forms) - [Planning Center 2](https://actionlake.com/connectors/planning-center) - [Hostaway 2](https://actionlake.com/connectors/hostaway) - [Make 2](https://actionlake.com/connectors/make) Joins with, on shared entities - [Lark Suite 2](https://actionlake.com/connectors/lark-suite) - [Clio Manage 2](https://actionlake.com/connectors/clio-manage) - [Nylas 2](https://actionlake.com/connectors/nylas) - [Luma 2](https://actionlake.com/connectors/luma) - [Acuity Scheduling 2](https://actionlake.com/connectors/acuity-scheduling) - [HaloPSA 1](https://actionlake.com/connectors/halopsa) Browse - [All Workspace connectors](https://actionlake.com/connectors/category/workspace) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Google Calendar; the name is the vendor's own. Counts are from the Google Calendar service file, version 1.0.0. ## Give your agent Google Calendar today. [Connect Google Calendar free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/google-calendar More: https://actionlake.com/llms.txt