Setup guide
Ask Claude when everyone is free and have it book the thing, without a single round of does-Tuesday-work emails.
Before you start
Google's own connector is in the directory, verified, and it manages your schedule. This page's route is a different shape: the whole Google Calendar tool list behind one endpoint, with you choosing which of it Claude can touch.
Google Calendar Verified
Versus
Connecting FloConnector connects Google Calendar, and Google Calendar is one of 60 connectors the same endpoint can carry. You do this setup once, not once per app.
Step one
Step two
Control
A profile carries only the tools you switch on, and the endpoint exposes only that profile. That is the whole permission model, and it is set before anyone connects.
Google Calendar Connected 11/45 7 read 4 write
Tick a row to include it, or flip Read only to lock every write off at once.
FloConnector holds the Google Calendar credential, encrypted before it is stored, and calls Google Calendar on the model's behalf. Claude sees the tools and their results, never the credential behind them.
Once it is connected
Each of these runs real Google Calendar tools, named underneath so you can see what Claude is actually calling. 11 of the 45 tools are covered here.
Find me an hour with Priya and Sam next week when none of us are booked.
The gaps where all three calendars are clear in that window, worked out from today's real date rather than an assumed one.
get_current_date_time list_calendars find_free_slots What have I got on tomorrow, across all my calendars?
Tomorrow's events from every calendar you subscribe to, merged into one list and shown in your own timezone.
get_current_date_time events_list_all_calendars Book the Meridian kickoff for Thursday at ten, invite the project team and put the dial-in in the description.
The event created with its attendees and description. Google sends the invitations from your account, because that is who the organiser is.
get_current_date_time create_event Move my Friday one-to-ones back an hour, all of them.
Each matching event shifted, one at a time, with the list read back so you can see exactly which ones moved.
find_event patch_event Which recurring meetings eat the most of my week?
Recurring series expanded into the instances that actually fall in the period and totalled by hours, so a fortnightly meeting is not counted as a weekly one.
events_list events_instances Set up a shared calendar for studio bookings and give the team edit access.
A new secondary calendar and one sharing rule per person, at the access level you asked for.
create_calendar acl_insert list_calendars Troubleshooting
Claude Desktop sits on Connect after you signed in
The sign-in has usually succeeded. Check the profile in your dashboard: if the grant is there the connection is live, and restarting the desktop app clears the stale button. It is a client-side issue, not something the server can fix.
The connector saves but no tools appear
Disconnect and reconnect it once. If it is still empty, check in the dashboard that the connection behind the profile is still connected and that you are an assigned member of that profile.
The first load is slow on a very large profile
A profile exposing hundreds of tools takes longer to load, and a model given too many tools chooses worse. Split the work across two profiles rather than exposing everything at once. This is the failure mode most MCP write-ups name and never solve.
No. You sign in on Google's own page and approve the permissions there. The token that comes back is encrypted before FloConnector stores it, and Claude only ever sees the tools and what they return.
Creating an event with attendees sends Google's own invitation, and it goes out under your name because you are the organiser. That is Google's behaviour rather than a setting of ours. If you want Claude proposing times but not booking them, leave the event-creation tool off and it will tell you the slot instead.
No. This connector reaches Google Calendar and nothing else in the Google account. Gmail is a separate connector with its own permissions, and whether a profile carries it is your decision.
Two ways. Connect the work account rather than the personal one, or leave the all-calendars tool off so Claude looks only where you point it. Google's own sharing settings still apply on top of both.
Anyone on the profile acts as the connected Google account and sees what it sees. If that is more than you want to hand over, connect a shared or delegated calendar account instead of your own and put them on that profile.
No, just the same URL in a different menu. A profile endpoint is a standard hosted MCP server, so nothing about the Google side changes.
Claude does not know what today is until something tells it, which is why the connector carries a tool that returns the current date and time in your timezone. Leave it switched on whatever else you enable. Without it, next Tuesday is a guess, and it is a guess that goes wrong most often on a Monday.
Free and busy slots come back only for calendars the connected account can already see. A colleague who has not shared theirs is simply invisible, and Claude will cheerfully offer a slot that is not free at all. Share the calendars first, or keep the question to your own.
Clearing a calendar deletes every event on it, and nothing brings them back. It sits in the picker alongside the ordinary event tools and it is needed for nothing routine, so leave it off and there is no route to it.
Your turn
One connection, one endpoint, and 45 Google Calendar tools your AI can actually run. Start free with 1,000 tool calls and see what your own first week looks like.
