Skip to content

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.

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
  • 38actionsin one signed file
  • 12readlook, never change
  • 19writecreate and update
  • 7wait for a yesdestructive, 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_tokenAccess token from one sign-in with your own OAuth app
    • refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
    • client_idGoogle OAuth client id
    • client_secretGoogle 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 callcheck { 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_tokenrefresh_tokenclient_idclient_secret
Limits we pace to
600 calls a minute, per connection
API covered
Google Calendar API 3www.googleapis.com/calendar/v3
Built from
Google Calendar's documentation, read 8 September 2026developers.google.com
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.

  • 12readlook, never change
  • 19writecreate and update
  • 7destructivewait 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.

ActionWhat it doesEffectSame name in
gws_calendar.events.listList calendar eventsList events on a calendar within a time window, optionally expanding recurrences.readcomm.event.list61 connectors
gws_calendar.calendar_list.listList the user's calendarsList every calendar in the authenticated user's calendar list, with their access roles.readcomm.calendar.list14 connectors
gws_calendar.events.importImport a calendar eventImport an existing event, preserving its original iCalendar UID.writecomm.event.create52 connectors
gws_calendar.acl.listList a calendar's access rulesList who may see or change a calendar, and at what level.readcomm.calendar_permission.list3 connectors
gws_calendar.events.deleteDelete a calendar eventRemove an event from a calendar.destructivecomm.event.delete45 connectors
gws_calendar.calendars.insertCreate a calendarCreate a new secondary calendar owned by the authenticated user.writecomm.calendar.create11 connectors
gws_calendar.acl.watchWatch a calendar's access rulesRegister a webhook channel to be notified when a calendar's sharing changes.writeautomation.webhook.create209 connectors
gws_calendar.events.watchWatch a calendar's eventsRegister a webhook channel to be notified when a calendar's events change.writeautomation.webhook.create209 connectors
gws_calendar.acl.getGet one calendar access ruleFetch a single sharing rule by its id.readcomm.calendar_permission.get2 connectors
gws_calendar.freebusy.queryQuery free/busy informationAsk when a set of calendars is busy across a time window.readcomm.availability.query5 connectors
gws_calendar.events.instancesList a recurring event's occurrencesList the individual occurrences a recurring event expands into.readcomm.event_instance.list3 connectors
gws_calendar.colors.getGet the calendar colour paletteFetch the fixed palette of colour ids calendars and events may use.readplatform.picklist_value.list52 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. Readread

    What is on the Google Calendar calendar this week?

    callsgws_calendar.events.list

  2. Plandestructive

    Cancel the remaining instances of a recurring meeting in Google Calendar. Ask me before anything is sent or changed.

    callsgws_calendar.events.getgws_calendar.events.instancesgws_calendar.events.patchgws_calendar.events.deletegws_calendar.events.list

  3. Plandestructive

    Remove a leaver's calendar access and hand over ownership in Google Calendar. Ask me before anything is sent or changed.

    callsgws_calendar.calendars.getgws_calendar.acl.getgws_calendar.acl.deletegws_calendar.calendars.transfer_ownershipgws_calendar.acl.list

  4. Writewrite

    Import a calendar event in Google Calendar. Show me exactly what you will send before you save it.

    callsgws_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 decidesBook '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 decidesGrant 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 decidesCancel 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 decidesDelete 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 eventgws_calendar.events.delete
  • Clear a calendargws_calendar.calendars.clear
  • Transfer a calendar's ownershipgws_calendar.calendars.transfer_ownership
  • Delete a calendargws_calendar.calendars.delete
  • Revoke access to a calendargws_calendar.acl.delete
  • Stop a calendar notification channelgws_calendar.channels.stop
  • Unsubscribe from a calendargws_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.

dogws_calendar.events.deleteconfirm_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: "[email protected]" },    { match: "gws_calendar.calendars.clear", approver: "[email protected]" },    { match: "gws_calendar.calendars.transfer_ownership", approver: "[email protected]" }  ]}
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.

  • 1upstream call per actionall 38 Google Calendar actions
  • 7actions pageeach page of a long list is one call
  • 12reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Google Calendar action.

38 actions by area: the id your agent calls, what it does, and its effect.

Calendar38
  • gws_calendar.acl.deleteRevoke access to a calendardestructive
  • gws_calendar.acl.getGet one calendar access ruleread
  • gws_calendar.acl.insertGrant access to a calendarwrite
  • gws_calendar.acl.listList a calendar's access rulesread
  • gws_calendar.acl.patchPatch a calendar access rulewrite
  • gws_calendar.acl.updateReplace a calendar access rulewrite
  • gws_calendar.acl.watchWatch a calendar's access ruleswrite
  • gws_calendar.calendar_list.deleteUnsubscribe from a calendardestructive
  • gws_calendar.calendar_list.getGet one calendar list entryread
  • gws_calendar.calendar_list.insertSubscribe to a calendarwrite
  • gws_calendar.calendar_list.listList the user's calendarsread
  • gws_calendar.calendar_list.patchPatch a calendar list entrywrite
  • gws_calendar.calendar_list.updateReplace a calendar list entrywrite
  • gws_calendar.calendar_list.watchWatch the user's calendar listwrite
  • gws_calendar.calendars.clearClear a calendardestructive
  • gws_calendar.calendars.deleteDelete a calendardestructive
  • gws_calendar.calendars.getGet a calendarread
  • gws_calendar.calendars.insertCreate a calendarwrite
  • gws_calendar.calendars.patchPatch a calendarwrite
  • gws_calendar.calendars.transfer_ownershipTransfer a calendar's ownershipdestructive
  • gws_calendar.calendars.updateReplace a calendarwrite
  • gws_calendar.channels.stopStop a calendar notification channeldestructive
  • gws_calendar.colors.getGet the calendar colour paletteread
  • gws_calendar.events.deleteDelete a calendar eventdestructive
  • gws_calendar.events.getGet one calendar eventread
  • gws_calendar.events.importImport a calendar eventwrite
  • gws_calendar.events.insertCreate a calendar eventwrite
  • gws_calendar.events.instancesList a recurring event's occurrencesread
  • gws_calendar.events.listList calendar eventsread
  • gws_calendar.events.moveMove a calendar event to another calendarwrite
  • gws_calendar.events.patchPatch a calendar eventwrite
  • gws_calendar.events.quick_addQuick-add a calendar event from textwrite
  • gws_calendar.events.updateReplace a calendar eventwrite
  • gws_calendar.events.watchWatch a calendar's eventswrite
  • gws_calendar.freebusy.queryQuery free/busy informationread
  • gws_calendar.settings.getGet one calendar preferenceread
  • gws_calendar.settings.listList calendar preferencesread
  • gws_calendar.settings.watchWatch calendar preferenceswrite

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.

Give your agent Google Calendar today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.