How do AI agents use Google Calendar through Open Connector?

Your user connects Google Calendar once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Calendar tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Google Calendar MCP server?

Yes. Open Connector can serve Google Calendar as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Calendar actions with credentials injected server-side.

Where do Google Calendar credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Google Calendar integration

Google Calendar integration for AI agents.

Google Calendar integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Calendar tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Google Calendar actions, managed and audited.

Your user connects Google Calendar once; your agent can then secure AI-agent actions — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Google Calendar access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Google Calendar tools.

38 tools are generated from the published Google Calendar catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 38 tools. All published catalog entries are included in this page's server-rendered HTML.

Calendar Acl Delete: Deletes an access control rule.; acl
Calendar Acl Get: Returns an access control rule.; acl
Calendar Acl Insert: Creates an access control rule.; acl
Calendar Acl List: Returns the rules in the access control list for the calendar.; acl
Calendar Acl Patch: Updates an access control rule. This method supports patch semantics.; acl
Calendar Acl Update: Updates an access control rule.; acl
Calendar Acl Watch: Watch for changes to ACL resources.; acl
Calendar CalendarList Delete: Removes a calendar from the user's calendar list.; calendarlist
Calendar CalendarList Get: Returns a calendar from the user's calendar list.; calendarlist
Calendar CalendarList Insert: Inserts an existing calendar into the user's calendar list.; calendarlist
Calendar CalendarList List: Returns the calendars on the user's calendar list.; calendarlist
Calendar CalendarList Patch: Updates an existing calendar on the user's calendar list. This method supports patch semantics.; calendarlist
Calendar CalendarList Update: Updates an existing calendar on the user's calendar list.; calendarlist
Calendar CalendarList Watch: Watch for changes to CalendarList resources.; calendarlist
Calendar Calendars Clear: Clears a primary calendar. This operation deletes all events associated with the primary calendar of an account.; calendars
Calendar Calendars Delete: Deletes a secondary calendar. Use calendars.clear for clearing all events on primary calendars.; calendars
Calendar Calendars Get: Returns metadata for a calendar.; calendars
Calendar Calendars Insert: Creates a secondary calendar. The authenticated user for the request is made the data owner of the new calendar. Note: We recommend to authenticate as the intended data owner of the calendar. You can use domain-wide delegation of authority to allow applications to act on behalf of a specific user. Don't use a service account for authentication. If you use a service account for authentication, the service account is the data owner, which can lead to unexpected behavior. For example, if a service account is the data owner, data ownership cannot be transferred.; calendars
Calendar Calendars Patch: Updates metadata for a calendar. This method supports patch semantics.; calendars
Calendar Calendars TransferOwnership: Transfers a secondary calendar between users within a Google Workspace organization. Requires user authentication with Manage Calendars administrator privilege, and one of the following authorization scopes: - https://www.googleapis.com/auth/calendar - https://www.googleapis.com/auth/calendar.calendars In the request, set useAdminAccess to true. The secondary calendar must be active to be transferred. Transferring disabled or deleted calendars isn't supported.; calendars
Calendar Calendars Update: Updates metadata for a calendar.; calendars
Calendar Channels Stop: Stop watching resources through this channel; channels
Calendar Colors Get: Returns the color definitions for calendars and events.; colors
Calendar Events Delete: Deletes an event.; events
Calendar Events Get: Returns an event based on its Google Calendar ID. To retrieve an event using its iCalendar ID, call the events.list method using the iCalUID parameter.; events
Calendar Events Import: Imports an event. This operation is used to add a private copy of an existing event to a calendar. Only events with an eventType of default may be imported. Deprecated behavior: If a non-default event is imported, its type will be changed to default and any event-type-specific properties it may have will be dropped.; events
Calendar Events Insert: Creates an event.; events
Calendar Events Instances: Returns instances of the specified recurring event.; events
Calendar Events List: Returns events on the specified calendar.; events
Calendar Events Move: Moves an event to another calendar, i.e. changes an event's organizer. Note that only default events can be moved; birthday, focusTime, fromGmail, outOfOffice and workingLocation events cannot be moved.; events
Calendar Events Patch: Updates an event. This method supports patch semantics.; events
Calendar Events QuickAdd: Creates an event based on a simple text string.; events
Calendar Events Update: Updates an event.; events
Calendar Events Watch: Watch for changes to Events resources.; events
Calendar Freebusy Query: Returns free/busy information for a set of calendars.; freebusy
Calendar Settings Get: Returns a single user setting.; settings
Calendar Settings List: Returns all user settings for the authenticated user.; settings
Calendar Settings Watch: Watch for changes to Settings resources.; settings

FAQ

Google Calendar integration, answered

How do AI agents use Google Calendar through Open Connector?: Your user connects Google Calendar once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Calendar tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Google Calendar MCP server?: Yes. Open Connector can serve Google Calendar as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Calendar actions with credentials injected server-side.
Where do Google Calendar credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Google Calendar — keep the keys.

Open source, self-hostable, with Google Calendar credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →