What can you do with the Google Calendar integration?

LiveContext exposes 37 operations on Google Calendar, covering event, acl, calendar and calendarlist. Common uses include calendar view, color pickers and voice assistants.

Which OAuth scopes does Google Calendar require?

It depends on the operation: each one declares the scopes Google Calendar requires for it. The most common are https://www.googleapis.com/auth/calendar (18 operations), https://www.googleapis.com/auth/calendar.events (8 operations), https://www.googleapis.com/auth/calendar.readonly (7 operations) and https://www.googleapis.com/auth/calendar.events.readonly (3 operations).

LiveContext

All integrations

Google Calendar integration

Calendar and scheduling service API for managing events, appointments, and calendars. Create, update, and delete events, manage multiple calendars, check availability, handle recurring events, and integrate with Google Meet. Perfect for building scheduling applications, calendar integrations, meeting management tools, and event automation systems.

37 toolsOAuthAPI docs

Connect Google Calendar How integrations work

Common Google Calendar use cases

calendar view
color pickers
voice assistants
calendar selector
calendar settings
event detail view
project calendars
quick name change
canceling meetings
meeting scheduling

What you can do with Google Calendar

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Event, 11 operations

POSTcreate_event
Creates a new calendar event with title, time, location, attendees, and reminders. Supports recurring events, Google Meet integration, and email notifications.
DELETEdelete_event
Deletes a calendar event. Can optionally send cancellation notifications to all attendees when removing a meeting.
GETget_event
Retrieves complete details of a specific calendar event including attendees, location, description, recurrence rules, and conference information.
POSTimport_event
Imports an event using its iCalendar UID. Creates a private copy that won't sync with the original. Useful for importing from external calendar systems.
GETlist_event_instances
Lists individual occurrences of a recurring event. Each instance can have its own modifications (time, location, cancelled status).
GETlist_events
Retrieves events from a calendar within a specified time range. Supports searching, filtering, and expanding recurring events into individual instances.
POSTmove_event
Moves an event from one calendar to another within the same account. Preserves all event details while changing the containing calendar.
PATCHpatch_event
Partially updates an event. Only modifies specified fields, preserving all other event properties.
POSTquick_add_event
Creates a calendar event using natural language text. Parses phrases like 'Meeting with John tomorrow at 3pm' to automatically set title, date, and time.
PUTupdate_event
Updates an existing calendar event. Can modify title, time, location, attendees, and other properties. Optionally sends update notifications to attendees.
POSTwatch_events
Creates a push notification channel to receive real-time updates when calendar events change (created, updated, deleted).

Acl, 7 operations

DELETEdelete_acl_rule
Removes a sharing rule, revoking access for the specified user, group, or domain.
GETget_acl_rule
Retrieves a specific sharing rule for a calendar showing the scope and permission level for that entity.
POSTinsert_acl_rule
Shares a calendar with a user, group, or domain by creating an access control rule. Specify the permission level from freeBusyReader to owner.
GETlist_acl
Lists all sharing rules for a calendar showing who has access and their permission level (owner, writer, reader, freeBusyReader).
PATCHpatch_acl_rule
Partially updates an access control rule. For ACL rules, this is functionally similar to update since only role can be modified.
PUTupdate_acl_rule
Updates an existing sharing rule to change the permission level for a user, group, or domain.
POSTwatch_acl
Creates a push notification channel for changes to calendar sharing rules (ACL changes).

Calendar, 7 operations

POSTclear_calendar
Removes all events from a primary calendar. This is the only way to 'reset' a primary calendar since it cannot be deleted.
POSTcreate_calendar
Creates a new secondary calendar for organizing events separately from the primary calendar. Useful for work/personal separation or project-specific calendars.
DELETEdelete_calendar
Permanently deletes a secondary calendar and all its events. Cannot delete the user's primary calendar.
GETget_calendar
Retrieves metadata for a specific calendar including name, description, time zone, and access level. Use 'primary' for the user's main calendar.
GETlist_calendars
Retrieves all calendars the user has access to including primary, shared, and subscribed calendars. Essential for calendar selection interfaces and multi-calendar views.
PATCHpatch_calendar
Partially updates a calendar's metadata. Only modifies specified fields, leaving others unchanged.
PUTupdate_calendar
Updates a calendar's metadata including name, description, location, and timezone. Requires owner access to the calendar.

Calendarlist, 6 operations

DELETEdelete_calendar_list_entry
Removes a calendar from the user's calendar list. For shared/subscribed calendars, this unsubscribes. For owned calendars, only removes from list (calendar still exists).
GETget_calendar_list_entry
Returns a specific calendar from the user's calendar list with display settings, color, and notification preferences.
POSTinsert_calendar_list_entry
Subscribes to an existing calendar by adding it to the user's calendar list. Use this to add shared calendars or public calendars.
PATCHpatch_calendar_list_entry
Partially updates a calendar's display settings. Only modifies specified fields, preserving others.
PUTupdate_calendar_list_entry
Updates how a calendar is displayed in the user's calendar list including color, visibility, custom name, and default reminders.
POSTwatch_calendar_list
Creates a push notification channel for changes to the user's calendar list (calendars added, removed, or updated).

Setting, 3 operations

GETget_setting
Retrieves a specific user setting like timezone, date format, or week start day.
GETlist_settings
Retrieves all user settings for Google Calendar including timezone, date format, time format, and notification preferences.
POSTwatch_settings
Creates a push notification channel for changes to user's Calendar settings.

Channel, 1 operation

POSTstop_channel
Stops a push notification channel, unsubscribing from further updates for events, calendar list, ACL, or settings.

Color, 1 operation

GETlist_colors
Retrieves the available color palette for calendars and events. Returns color IDs with their background and foreground hex values for UI rendering.

Freebusy, 1 operation

POSTget_freebusy
Checks availability across multiple calendars for a given time range. Returns busy time blocks for scheduling meetings when participants are free.

OAuth scopes Google Calendar requires

Each operation declares the scopes Google Calendar requires for it.

https://www.googleapis.com/auth/calendarneeded by clear_calendar, create_calendar, delete_acl_rule and 15 more
https://www.googleapis.com/auth/calendar.eventsneeded by create_event, delete_event, import_event and 5 more
https://www.googleapis.com/auth/calendar.readonlyneeded by get_acl_rule, get_calendar, get_calendar_list_entry and 4 more
https://www.googleapis.com/auth/calendar.events.readonlyneeded by get_event, list_event_instances, list_events
https://www.googleapis.com/auth/calendar.acls.readonlyneeded by list_acl

Use Google Calendar from Claude Code, Cursor or Codex

Connect Google Calendar in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Calendar operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google Calendar

Create your workspace
Sign up free. Nothing to install.
Connect Google Calendar once
Add your Google Calendar connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Google Calendar integration FAQ

What can you do with the Google Calendar integration?: LiveContext exposes 37 operations on Google Calendar, covering event, acl, calendar and calendarlist. Common uses include calendar view, color pickers and voice assistants.
Which OAuth scopes does Google Calendar require?: It depends on the operation: each one declares the scopes Google Calendar requires for it. The most common are https://www.googleapis.com/auth/calendar (18 operations), https://www.googleapis.com/auth/calendar.events (8 operations), https://www.googleapis.com/auth/calendar.readonly (7 operations) and https://www.googleapis.com/auth/calendar.events.readonly (3 operations).