Google Calendar MCP integration for AI agents.
A Google Calendar MCP integration for AI agents to inspect calendars, check availability, and create or update reviewed events through permission-aware actions.
- ACTION CONTRACTS
- 38
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Google Calendar integration exposes
The Working Machines Google Calendar Agent App lets an authorized agent list calendars, inspect events, and check scheduling context before proposing a change. Stable calendar and event identifiers keep follow-up actions attached to the intended resource.
Calendar data can reveal locations, participants, customer relationships, and confidential plans. Read the minimum date range needed, distinguish free-busy checks from event content, and confirm attendees, time zones, recurrence, and notifications before creating or changing an event.
VERIFIED ACTION SAMPLE
Real Google Calendar capabilities.
Showing 12 of 38 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
add_calendar_to_listREADAdd a calendar to the current user's Google Calendar list.
INPUTS: calendarId
add_attendeeWRITEAdd one attendee to a Google Calendar event without replacing existing guests.
INPUTS: eventId / attendeeEmail / calendarId / sendUpdates / displayName
delete_acl_ruleHIGH IMPACTDelete an ACL rule from a Google Calendar.
INPUTS: calendarId / ruleId
clear_calendarREVIEWClear all events from a Google Calendar.
INPUTS: calendarId
create_acl_ruleWRITECreate an ACL rule on a Google Calendar.
INPUTS: calendarId / rule
create_calendarWRITECreate a Google Calendar.
INPUTS: summary / description / location / timeZone
create_eventWRITECreate a Google Calendar event.
INPUTS: calendarId / event / sendUpdates
delete_calendarHIGH IMPACTDelete a Google Calendar.
INPUTS: calendarId
delete_eventHIGH IMPACTDelete a Google Calendar event.
INPUTS: calendarId / eventId / sendUpdates
find_eventREADSearch events in a Google Calendar using a query string.
INPUTS: query / calendarId / timeMin / timeMax / updatedMin
find_free_slotsREADDerive free slots from Google Calendar freeBusy data.
INPUTS: items / timeMin / timeMax / timeZone / groupExpansionMax
free_busy_queryREADQuery busy intervals for calendars and groups.
INPUTS: items / timeMin / timeMax / timeZone / groupExpansionMax
INPUT CONTRACTS
Know what the action needs before it runs.
add_calendar_to_list
calendarIdREQUIRED- Google Calendar ID. Omit to use the primary calendar when supported.
add_attendee
eventIdREQUIRED- Google Calendar event ID.
attendeeEmailREQUIRED- Attendee email address to add.
calendarIdOPTIONAL- Google Calendar ID. Omit to use the primary calendar when supported.
sendUpdatesOPTIONAL- Who should receive invitation or update emails. Defaults to all so the new guest is notified.
displayNameOPTIONAL- Attendee display name.
delete_acl_rule
calendarIdREQUIRED- Google Calendar ID. Omit to use the primary calendar when supported.
ruleIdREQUIRED- Google Calendar ACL rule ID.
clear_calendar
calendarIdREQUIRED- Google Calendar ID. Omit to use the primary calendar when supported.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Availability research
Inspect only the calendars and time window needed to propose meeting options.
Meeting creation
Create an event after the organizer, attendees, time zone, duration, and conference settings are approved.
Meeting follow-through
Use a verified event as the anchor for notes, tasks, and participant communication in other Agent Apps.
SAFETY BOUNDARY
Operate Google Calendar with explicit limits
- Use free-busy data when event details are unnecessary.
- Confirm calendar, attendees, date, time zone, recurrence, and notifications.
- Do not infer attendee consent from calendar availability.
- Verify the returned event ID and canonical link after a write.
CONNECTION MODEL
OAuth 2.0
Google Calendar uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 18
- WRITE SIGNALS
- 10
- HIGH IMPACT
- 5
- REVIEW SIGNALS
- 5
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Google Calendar.