Google Calendar
MCP server for Google Calendar integration - manage events, schedules, and calendar data
Tools
13 available tools
Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.
13 tools found.
Create Calendar
Tool name:
create_calendarCreate a new calendar.
Create event
Tool name:
create_eventCreate a new event in your Google Calendar with detailed options including attendees, location, reminders, and recurrence rules.
Delete Calendar
DestructiveTool name:
delete_calendarDelete a secondary calendar.
Delete event
DestructiveTool name:
delete_eventDelete an event from your calendar.
Get event
Read onlyTool name:
get_eventGet detailed information about a specific calendar event including title, description, time, location, attendees, and recurrence rules.
Get free busy
Read onlyTool name:
get_free_busyCheck free/busy information for calendars within a time range.
List calendars
Read onlyTool name:
list_calendarsList all calendars accessible to the authenticated user.
List events
Read onlyTool name:
list_eventsList events from your Google Calendar.
Move event
Tool name:
move_eventMove an event from one calendar to another.
Add quick
Tool name:
quick_addQuickly add an event using natural language text (e.g., 'Lunch with Sarah tomorrow at 12pm' or 'Team meeting Friday 2-3pm').
Respond to event
Tool name:
respond_to_eventRespond to a calendar invitation on behalf of the authenticated attendee.
Update Calendar
Tool name:
update_calendarUpdate calendar settings such as name, description, or timezone.
Update event
Tool name:
update_eventUpdate an existing calendar event.
Compatibility
Connect Google Calendar to the clients your teams already use
27 AI clients can connect to Google Calendar through Runlayer. Pick one for its setup steps and controls.
Why Runlayer
Why connect Google Calendar through Runlayer?
One approved path
Approve Google Calendar once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.
Fine-grained policy
Control who can use each server, tool, and resource, and under which runtime conditions.
Runtime security
Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.
Audit and observability
Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.