Connect Google Calendar to Claude Code
Read calendars, check availability, and create, update, or cancel events. Add Toolspoke to Claude Code once and it can use 8 Google Calendar actions. Your Google Calendar credential stays in Toolspoke, and you choose which actions Claude Code may call.
Set it up in Claude Code
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Claude Code
Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcpThe sign-in opens in your browser, and Toolspoke asks you to approve it.
Install Google Calendar and connect it
Add Google Calendar to a project in your Toolspoke workspace.
Press connect and sign in to Google Calendar. Toolspoke keeps the token encrypted and refreshes it when it expires, so there is nothing to copy and nothing to rotate by hand.
Choose what Claude Code may do
All 8 actions start on. Switch off any of the 4 actions that change something in Google Calendar, and Claude Code gets a refusal if it tries.
What you can ask Claude Code for
A few of the Google Calendar actions that only read, so they are safe to try first.
- List the calendars this account can see, with their IDs, time zones and access roles
- List events on one calendar within a time window
- Fetch one event by ID, summary, description, location, start and end, recurrence, and its organiser
- Answer "when is this free" across one or more calendars at once
What Claude Code can do in Google Calendar
4 actions read, 2 write and 2 delete or permanently change something.
Reads
List calendars
List the calendars this account can see, with their IDs, time zones and access roles. Call it first when you do not know which calendar ID to use, or to find out whether the connection can write to a calendar at all, accessRole "reader" means it cannot.
List events
List events on one calendar within a time window. Recurring events are expanded into their individual occurrences and ordered by start time, so "what is on Thursday" is answered directly. Times are RFC 3339 with an offset, e.g. 2026-08-20T09:00:00+05:30.
Get event
Fetch one event by ID, summary, description, location, start and end, recurrence, and its organiser. Event IDs come from list_events.
Find free time
Answer "when is this free" across one or more calendars at once. Returns only busy intervals, start and end times with nothing about what the events are, which is what makes it the right call for scheduling against a colleague's calendar you can see but should not read.
Writes
Create event
Put an event on a calendar. This writes to the calendar and notifies nobody, it cannot invite anyone, and sendUpdates is pinned to none. Use invite_to_event to add attendees, which is classified destructive because it reaches people outside the workspace.
Update event
Change an existing event's title, description, location or times. This writes to the calendar and notifies nobody, it cannot invite anyone, and sendUpdates is pinned to none. Use invite_to_event to add attendees, which is classified destructive because it reaches people outside the workspace. Only the fields passed are altered.
Deletes or permanently changes
Invite to event
Invite people to an existing event, and optionally email them about it. Adding an attendee puts the event on someone else's calendar and send_updates: "all" mails them, both of which reach outside the workspace, the same class of act as sending mail, which is why this is destructive rather than a write. A write grant can create and edit events but cannot reach this. NOTE: the attendee list is REPLACED, not appended: fetch the event with get_event first and pass the existing attendees alongside the new ones, or the people already on it are silently uninvited.
Delete event
Cancel an event and remove it from the calendar. Classified destructive, so a write grant cannot reach it and an install has to grant full access or name it explicitly. send_updates decides whether attendees are told it was cancelled, and defaults to none.
Google Calendar in Claude Code: questions
Does Claude Code see my Google Calendar credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Can I stop Claude Code from changing things in Google Calendar?
Yes. Each of the 8 actions can be switched off for a project. Turn off the 4 that change something and Claude Code can only read.
Will 8 actions crowd Claude Code's context?
No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Google Calendar action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Can I add it once for every project?
Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.
What does it cost?
Tool calls are free on every plan, and a Google Calendar call does not run in a sandbox, so it bills nothing.
Google Calendar in your other apps
Try Google Calendar in Claude Code
Free to start, and tool calls cost nothing on any plan.