# How do ops teams use Google Calendar in Claude?

> An ops team can use Google Calendar in Claude to find free time and book meetings. Each coordinator signs in to Google, and sharing tools stay restricted.

**TL;DR** An operations team can put Google Calendar in Claude through Elaichi's googlecalendar connector, with each coordinator signed in to their own Google account so that Google's sharing decides whose calendars they see. Free/busy, event and attendee reads stay open, and event create and update cover booking. Block rules restrict the tools that share a calendar, clear its events or delete it, starting with create_a_googlecalendar_acl, which sits in the write tier and can share a calendar with the public.

## Why an operations team wants Google Calendar in Claude

Emily Carter coordinates schedules for a 60-person operations team. Most of her day is calendar questions. When are Jake Morgan, Marcus Reed and Olivia Bennett all free next week for the vendor review? Did the warehouse leads accept Thursday's safety walk? Can she book 45 minutes with finance before Friday? Each answer means opening several calendars and an event page. With Google Calendar in Claude, she asks once, in the chat where she is already writing the agenda.

MCP (Model Context Protocol) is the standard way an AI assistant calls tools in other apps. [Elaichi's `googlecalendar` connector](/connectors/googlecalendar/) signs in to Google with OAuth, the sign-in where a person approves an app on their own account. It carries free/busy, event and attendee reads, event writes, and tools that change who can see a calendar. Most of Emily's work needs the reads and two booking tools. A few sharing and delete tools need a rule before the team gets access.

## One Google sign-in per coordinator, or one shared account?

Give each coordinator their own Google Calendar connection. In Elaichi, every call through a connection runs on that connection's Google sign-in, whoever is calling. So the account behind the connection decides whose calendars Claude can see, and which account creates each meeting.

A shared connection runs everyone's calls as its owner. Emily's teammates would see what the owner's Google account sees, including every calendar shared with that person. Every meeting they book would be created by that account too. Google's events reference says an event's organizer is read-only, except when importing an event ([developers.google.com](https://developers.google.com/workspace/calendar/api/v3/reference/events), checked November 2026). Fixing the wrong organizer later is not a simple edit.

Per-person sign-in keeps Google's own sharing in charge. Jake shares his calendar with Emily in Google Calendar, at a level such as See only free/busy, See event details or Make changes and manage sharing ([support.google.com](https://support.google.com/calendar/answer/37082?hl=en), checked November 2026). Emily then reaches exactly that through Claude, and nothing more. To save each coordinator the setup, share a template at `use`. Each person stamps their own toolbox from it and picks their own connection. [Agent access that follows each employee's permissions](/blog/ai-agents-employee-permissions/) covers that pattern.

## Finding a time when five people are free

Ask Claude for free/busy, not for event lists. `list_all_googlecalendar_free_busy` takes a start time, an end time and the calendars to check. It returns busy ranges for each calendar, plus any errors for each. Google caps one query at 50 calendars and a group expansion at 100 members ([developers.google.com](https://developers.google.com/workspace/calendar/api/v3/reference/freebusy/query), checked November 2026).

Free/busy needs less sharing than reading events. Google's freeBusyReader role shows whether a calendar is free or busy at a given time, without event details ([developers.google.com](https://developers.google.com/workspace/calendar/api/concepts/sharing), checked November 2026). Workspace admins also set a default internal sharing level: No sharing, Only free/busy information or Share all information ([knowledge.workspace.google.com](https://knowledge.workspace.google.com/admin/calendar/set-google-calendar-sharing-options?hl=en), checked November 2026). If Marcus's calendar comes back with an error, check his sharing before blaming Claude.

`list_all_googlecalendar_events` is the wrong tool for this question. It takes a calendar id, a limit and a paging cursor, with no start or end time. It cannot ask Google for one week alone, so availability questions belong with free/busy.

## Who accepted the meeting?

Read the event, then read each attendee's response. `get_single_googlecalendar_event_by_id` returns one event's title, time, attendees, location and description. It needs the id of the calendar that owns the event. Google lists four response states for an attendee: needsAction, declined, tentative and accepted. needsAction means the person has not responded yet ([developers.google.com](https://developers.google.com/workspace/calendar/api/v3/reference/events), checked November 2026).

For a weekly meeting, ask about one occurrence rather than the series. `list_all_googlecalendar_event_instances` lists each occurrence of a recurring event in a time range. These questions are all reads, so they run under every rule in this post.

## Booking the meeting, and who gets told

Booking takes `create_a_googlecalendar_event`, which needs a calendar id, a start and an end. It also takes attendees, a recurrence rule and conference data for a Google Meet link. Rescheduling takes `update_a_googlecalendar_event_by_id`, a PATCH that changes only the fields Claude sends.

Notifications need a test before rollout. Elaichi's create, update and delete event tools take no `sendUpdates` argument. Google's events.insert reference says `sendUpdates` sets who is notified about a new event, that the default is false, and that some emails might still be sent ([developers.google.com](https://developers.google.com/workspace/calendar/api/v3/reference/events/insert), checked November 2026). Two other tools, `googlecalendar_events_quick_add` and `googlecalendar_events_move`, do take `sendUpdates`. Book a test meeting with a colleague and see what arrives before the team relies on it.

The update tool carries one more power. Its status field accepts `cancelled`, and Google's events reference says a cancelled event is deleted ([developers.google.com](https://developers.google.com/workspace/calendar/api/v3/reference/events), checked November 2026). So blocking the delete tool alone does not stop a cancellation. Whoever can reschedule can also cancel.

## Which Google Calendar tools can share or wipe a calendar?

Three groups change more than one meeting: the sharing tools, the calendar clear and the deletes. Elaichi tiers six Google Calendar tools as destructive. The riskiest tool is not among them.

`create_a_googlecalendar_acl` is tiered write. It creates a sharing rule with a role of none, freeBusyReader, reader, writer or owner. The rule applies to a user, a group, a domain or the `default` scope. Google's ACL reference says `default` is the public scope and applies to any user, authenticated or not. An owner can also change other people's access ([developers.google.com](https://developers.google.com/workspace/calendar/api/v3/reference/acl), checked November 2026). One call can publish a calendar or hand someone control of it. Its `sendNotifications` argument defaults to true, so Google announces the change unless told not to.

`googlecalendar_calendars_clear` deletes every event on the calendar it names and leaves the calendar, its description says, and the clear cannot be undone. Google's reference describes clear as deleting all events on an account's primary calendar ([developers.google.com](https://developers.google.com/workspace/calendar/api/v3/reference/calendars/clear), checked November 2026). On a primary calendar, that is every meeting the person has.

A Workspace admin setting adds a ceiling. Google's sharing guide says domain settings can cap sharing. When the domain allows only free/busy sharing, outsiders see only free/busy even on a public calendar ([developers.google.com](https://developers.google.com/workspace/calendar/api/concepts/sharing), checked November 2026). Treat that as a second wall, not the first.

| Kind | Tools | Tier | For the ops role |
|---|---|---|---|
| Availability and event reads | `list_all_googlecalendar_free_busy`, `list_all_googlecalendar_calendar_lists`, `get_single_googlecalendar_event_by_id`, `list_all_googlecalendar_event_instances` | read | Allow |
| Booking | `create_a_googlecalendar_event`, `update_a_googlecalendar_event_by_id`, `googlecalendar_events_quick_add` | write | Allow |
| Sharing | `create_a_googlecalendar_acl`, `update_a_googlecalendar_acl_by_id` | write | Restrict |
| Sharing removal | `delete_a_googlecalendar_acl_by_id` | destructive | Restrict |
| Clear and delete | `googlecalendar_calendars_clear`, `delete_a_googlecalendar_calendar_by_id`, `delete_a_googlecalendar_event_by_id` | destructive | Restrict |
| Contacts | `delete_a_googlecalendar_search_contact_by_id` | destructive | Restrict |

## Writing the Google Calendar rules on the ops role

Put block rules on the operations role, and name every write the team does not need. In Elaichi, restriction targets are role or user only; the organization default is the absence of a rule, which means allow everything, so these rules belong on a role that only the operations team holds. A restriction is a rule naming which connectors and which individual tools a target may reach.

Block-only rules leave gaps unless the list is complete. In Elaichi, a layer with only block rules has no allowlist, so everything it does not block passes it. So name the three sharing tools, the clear, the calendar and event deletes, the contact delete and the calendar-list delete. Name the rest of the write tier too: calendar create and update, calendar-list create and update, event import and move, the four watch tools and `googlecalendar_channels_stop`. That leaves the reads and the three booking tools.

The other shape is an allow rule naming the reads and the booking tools. In Elaichi, once a role carries any allow rule, every connector and tool none of its allow rules names is blocked for that role. The operations role would then need whole-connector allow rules for every other app it uses. [Per-tool versus per-app restrictions](/blog/per-tool-vs-per-app-restrictions/) weighs the two shapes. A restriction change takes effect within about two minutes.

Keep the event delete restricted even though update can cancel. If canceling must stay with one coordinator, block update on the role as well. That costs everyone else on the role the ability to reschedule, so make the choice on purpose. The coordinator files an access request for it. Only an admin in the Elaichi console can approve it, under Governance, then Access requests. Approval creates an access grant for that one person and leaves the role's rules unchanged. A grant approved in the console has no end date.

## Add Elaichi in Claude and test a booking

Every organization uses one address: `https://api.elaichi.ai/mcp`. Add it in Claude, and each member signs in to Elaichi with their own OAuth grant, the sign-in that ties their Elaichi identity to that client. [Connecting Elaichi to Claude](/blog/connect-elaichi-to-claude/) shows the screens. The same address serves ChatGPT, Cursor and Microsoft Copilot.

In Elaichi, connected tools are never listed one by one, however few there are. Claude finds the calendar tools with `search_tools`, runs reads with `read_tool` and runs writes with `execute_tool`. No consent checkbox holds Claude to reading a connected app, so the block rules carry the weight.

Test from a coordinator's account. Ask when three colleagues are free next Thursday, then book a 30-minute test meeting with one of them. Search for "acl" next. A restricted tool is left out of the tools Elaichi offers a client and cannot be called. Search still names it, flagged restricted, with no schema. Then read the audit log. Elaichi writes one entry for each connected-tool call that reaches execution (a call refused earlier writes none). In Elaichi, a call from an MCP client is recorded under the person who signed in, with surface `mcp` and the OAuth client named. [What an AI audit log must capture](/blog/what-an-ai-audit-log-must-capture/) lists what to check in each row.

## When Claude's own Google Calendar connector is enough

If one person wants their own calendar in Claude, Claude already has a connector for it. Anthropic says its Gmail, Google Calendar and Google Drive connectors are available to all Claude users. On Team and Enterprise plans, an Owner enables them before members can sign in. Claude mirrors each user's existing Google Workspace permissions ([support.claude.com](https://support.claude.com/en/articles/10166901-use-google-workspace-connectors), checked October 2026). Team and Enterprise Owners can set a connector's tools to Always allow, Needs approval or Blocked ([support.claude.com](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities), checked October 2026).

Google also documents its own Calendar MCP server. It is a Developer Preview that needs membership of the Google Workspace Developer Preview Program. Adding it to Claude takes your own OAuth client ID and secret, on a Claude Enterprise, Pro, Max or Team plan. Its tools include `list_events`, `suggest_time`, `create_event` and `delete_event` ([developers.google.com](https://developers.google.com/workspace/calendar/api/guides/configure-mcp-server), checked November 2026).

Elaichi earns its place when the team works across clients and apps. One endpoint serves Claude, ChatGPT, Cursor and Microsoft Copilot. One set of role rules covers Google Calendar beside every other connector, and one audit trail records who booked what. Teams on ChatGPT can follow [the Gmail and Calendar setup for ChatGPT](/blog/connect-gmail-and-google-calendar-to-chatgpt/). For one person trying a few questions, [you may not need a control plane yet](/blog/when-you-dont-need-an-mcp-gateway/). Browse the [900+ connectors](/connectors/) for the rest of the operations stack.

## FAQ

### Does Google Calendar have its own MCP server?

Google documents a Calendar MCP server as a Developer Preview, available through the Google Workspace Developer Preview Program (checked November 2026). Adding it to Claude.ai or Claude Desktop takes a custom connector with your own OAuth client ID and secret, on a Claude Enterprise, Pro, Max or Team plan. Its page lists tools such as list_events, suggest_time, create_event and delete_event.

### Can Claude see a colleague's Google Calendar?

Claude sees only what the Google account behind the connection can see. In Google Calendar, a colleague shares a calendar at a level such as See only free/busy, See event details or Make changes and manage sharing, and a Workspace administrator decides whether sharing is allowed at all (checked November 2026). With free/busy access, Google's free/busy query returns busy times without event details.

### Does an event created from Claude email the attendees?

Elaichi's create_a_googlecalendar_event tool takes no sendUpdates argument. Google's events.insert reference says sendUpdates sets who is notified about a new event, that the default is false, and that some emails might still be sent (checked November 2026). Book a test meeting with a colleague before rollout and check what arrives.

### What does googlecalendar_calendars_clear do?

The description of Elaichi's googlecalendar_calendars_clear tool says it deletes every event on the calendar it names, leaves the calendar itself, and cannot be undone. Google's calendars.clear reference describes the method as deleting all events on an account's primary calendar (checked November 2026). An operations role should keep it restricted.

## Read next

- [Gmail and Calendar MCP access for ChatGPT](/blog/connect-gmail-and-google-calendar-to-chatgpt/) — Gmail and Calendar MCP access for ChatGPT: each person signs in as themselves, and restrictions stop the AI sending or deleting mail.
- [Restrict one AI tool or the whole app? Six cases](/blog/per-tool-vs-per-app-restrictions/) — Restrict one AI tool when a role needs part of an app, and block the whole app when it needs none of it. Six cases, and what new tools do to each rule.
- [Connect Elaichi to Claude](/blog/connect-elaichi-to-claude/) — To connect Elaichi to Claude, add one URL as a custom connector and sign in with OAuth. On Team and Enterprise, an Owner adds it once for everyone.
