Google Calendar
Meetings, free/busy, scheduling.
Verdict
Common use cases
- Find open meeting slots across the team
- Create calendar invites from chat threads
- Pull weekly agendas into standup notes
- Reschedule conflicts when priorities shift
- Check attendee availability before booking
Integration
- Vendor
- Google Calendar
- Category
- productivity
- Auth
- OAUTH2
- Composio slug
google_calendar
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Browse MCPs. 2. Search for Google Calendar and click Connect. 3. You'll be redirected to Google's OAuth consent screen — sign in with the Google account that owns or has edit access to the calendars you want Switchy to manage. 4. Review the requested scopes: Switchy needs 'See and edit events on all your calendars' to create, update, and query events. 5. Click Allow to grant permissions. 6. You'll return to Switchy with a confirmation that Google Calendar is connected. 7. Open any Space and type '@Google Calendar what's on my calendar tomorrow?' — if the MCP replies with your agenda, the connection works. 8. To invoke tools, @mention Google Calendar in a message and describe the task (e.g. 'schedule a 30-minute sync with alice@example.com next Tuesday afternoon').
What teammates see: by default, memories from Google Calendar are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Tomorrow's Schedule
@Google Calendar show me everything on my calendar tomorrow, including meeting titles and timesOpen in a Space →
Find Meeting Slots
@Google Calendar find three 30-minute slots next week when sarah@example.com, mike@example.com, and I are all availableOpen in a Space →
Create Team Sync
@Google Calendar schedule a weekly team sync every Monday at 10am starting next week, invite the whole product teamOpen in a Space →
Reschedule Conflict
@Google Calendar move my 2pm client call on Thursday to Friday at the same time and notify attendeesOpen in a Space →
Summarize This Week
@Google Calendar list every meeting on my calendar this week with attendees and durationsOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@google-calendar show me all meetings scheduled for next Tuesday and highlight any conflicts with my focus blocks
Found 7 events on Tuesday, March 18. Three meetings overlap with your designated focus time: a 10am product sync conflicts with your 9-11am deep work block, and back-to-back 2pm and 3pm calls run into your 2-4pm coding window. The morning standup at 9:30am and end-of-day retro at 5pm fall outside focus periods. Two personal appointments (dentist at 1pm, gym at 6pm) are also on the calendar.
This example shows read access across a full day with basic conflict detection. Requires calendar.readonly or calendar.events OAuth scope. The MCP returns event metadata (title, time, attendees) but cannot infer 'focus blocks' unless you've labeled them consistently in event titles or descriptions.
@google-calendar create a 30-minute one-on-one with jordan.lee@company.com tomorrow at 3pm, title it 'Q1 Planning Check-in' and add a Google Meet link
Created event 'Q1 Planning Check-in' on March 15 at 3:00-3:30pm. Invited jordan.lee@company.com as a required attendee. Generated and attached a Google Meet conference link. Calendar invitation sent to Jordan; you'll receive a confirmation email. Event ID: abc123xyz for future reference or edits.
Demonstrates event creation with conferencing. Requires calendar.events OAuth scope (write access). The MCP will fail if Jordan's email is outside your organization and external sharing is disabled. Meet link generation depends on your Google Workspace settings allowing automatic conferencing.
@google-calendar pull all meetings from the last two weeks where 'budget' appears in the title or description, then summarize key decisions mentioned in event notes
Located 4 events matching 'budget': Feb 28 Finance Review, March 4 Q1 Budget Planning, March 6 Department Allocation Call, March 11 Budget Finalization. Event descriptions mention: approval of $50k additional headcount spend (March 4), deferral of new tooling purchases to Q2 (March 6), final sign-off on revised forecast with 8% contingency (March 11). No notes captured for the Feb 28 meeting.
Combines search with AI synthesis of freeform text. Requires calendar.readonly scope. Quality depends on how much detail attendees add to event descriptions—many organizations leave these fields empty. The MCP cannot access meeting transcripts or attached documents, only calendar metadata and description fields.
Use-case deep-dives
When Google Calendar MCP handles recurring standup logistics
A 6-person design team runs three standups a week and needs to shift times when people travel or take PTO. The Google Calendar MCP lets your AI workspace read availability, propose new slots, and update recurring events without opening the calendar UI. OAuth2 means each team member authenticates once and the workspace respects their individual permissions. This works when your team already lives in Google Workspace and standup timing changes at least twice a month. If you're scheduling external stakeholders or need Zoom link generation, you'll hit the MCP's read-heavy scope and need the native app for meeting setup. Use this MCP when your bottleneck is internal coordination, not external booking.
Where Calendar MCP falls short for milestone management
A 3-person consulting shop tracks client deliverable dates in Google Calendar and wants the AI to surface upcoming deadlines during planning chats. The Calendar MCP can pull event lists and check conflicts, but it's not built for task dependencies or status tracking. You'll get event titles and times, but no way to mark a milestone complete or roll dates when scope changes. If your calendar events are just reminders and the real project state lives in Notion or Linear, the MCP becomes a read-only reference that duplicates better tools. Skip this integration unless your team genuinely uses calendar events as the source of truth for what's due and when.
When Calendar MCP streamlines on-call rotation lookups
A 12-person support team rotates on-call coverage and logs shift swaps in a shared Google Calendar. The MCP lets your AI workspace answer "who's on-call this weekend" or "when does Sarah's next shift start" without leaving the chat. OAuth2 means the workspace sees only calendars each person has access to, so junior reps can't query executive schedules. This setup wins when shift changes happen in Slack and you need instant answers without opening a browser tab. If your rotation logic involves PagerDuty or Opsgenie, those tools own the schedule and the Calendar MCP just mirrors stale data. Use this when Google Calendar is the actual rotation system, not a backup view.
Frequently asked
What does the Google Calendar MCP let me do in Switchy?
It connects your Google Calendar account so AI agents in Switchy can read your schedule, create events, update meetings, and check availability. You grant OAuth access once, then any team member with workspace permissions can ask the AI to manage calendar tasks without leaving the conversation. The MCP handles authentication and API calls in the background.
Which Google Calendar permissions does Switchy request during OAuth?
Switchy requests calendar read and write scopes during the OAuth flow. You'll see a Google consent screen listing the specific permissions—typically calendar.events and calendar.readonly. You can revoke access anytime from your Google Account security settings. The MCP doesn't request contacts, email, or Drive access.
Can the Google Calendar MCP create recurring events or manage shared calendars?
Yes, if the underlying Google Calendar API supports it and your OAuth token includes the necessary scopes. The MCP can create recurring events with standard patterns and interact with calendars you own or have write access to. It respects the same permission boundaries you'd see in the Google Calendar web interface.
Why use this MCP instead of just opening Google Calendar in a browser tab?
The MCP lets AI agents schedule meetings, check conflicts, and update events directly from chat—no context switching. Instead of describing what you need then manually creating the event, you ask once and the agent does it. Useful when coordinating across multiple calendars or building workflows that combine calendar data with other tools.
Who on my team should connect the Google Calendar MCP?
Anyone who wants AI agents to manage their personal calendar. Each connection is tied to one Google account, so if your team shares a group calendar, the person with edit access should connect it. Multiple team members can connect their own calendars to the same Switchy workspace without conflicts.