Google Meet integration for AI agents.
Google Meet 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 Meet 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.
Real Google Meet actions, managed and audited.
Your user connects Google Meet 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 Meet 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.
Supported Google Meet tools.
11 tools are generated from the published Google Meet catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 11 tools. All published catalog entries are included in this page's server-rendered HTML.
- Meet ConferenceRecords List
- Lists the conference records. By default, ordered by start time and in descending order.
- conferencerecords
- Meet ConferenceRecords Participants List
- Lists the participants in a conference record. By default, ordered by join time and in descending order. This API supports `fields` as standard parameters like every other API. However, when the `fields` request parameter is omitted, this API defaults to `'participants/*, next_page_token'`.
- conferencerecords
- Meet ConferenceRecords Participants ParticipantSessions List
- Lists the participant sessions of a participant in a conference record. By default, ordered by join time and in descending order. This API supports `fields` as standard parameters like every other API. However, when the `fields` request parameter is omitted this API defaults to `'participantsessions/*, next_page_token'`.
- conferencerecords
- Meet ConferenceRecords Recordings List
- Lists the recording resources from the conference record. By default, ordered by start time and in ascending order.
- conferencerecords
- Meet ConferenceRecords SmartNotes List
- Lists the set of smart notes from the conference record. By default, ordered by start time and in ascending order.
- conferencerecords
- Meet ConferenceRecords Transcripts Entries Get
- Gets a `TranscriptEntry` resource by entry ID. Note: The transcript entries returned by the Google Meet API might not match the transcription found in the Google Docs transcript file. This can occur when 1) we have interleaved speakers within milliseconds, or 2) the Google Docs transcript file is modified after generation.
- conferencerecords
- Meet ConferenceRecords Transcripts Entries List
- Lists the structured transcript entries per transcript. By default, ordered by start time and in ascending order. Note: The transcript entries returned by the Google Meet API might not match the transcription found in the Google Docs transcript file. This can occur when 1) we have interleaved speakers within milliseconds, or 2) the Google Docs transcript file is modified after generation.
- conferencerecords
- Meet ConferenceRecords Transcripts List
- Lists the set of transcripts from the conference record. By default, ordered by start time and in ascending order.
- conferencerecords
- Meet Spaces Create
- Creates a space.
- spaces
- Meet Spaces EndActiveConference
- Ends an active conference (if there's one). For an example, see [End active conference](https://developers.google.com/workspace/meet/api/guides/meeting-spaces#end-active-conference).
- spaces
- Meet Spaces Patch
- Updates details about a meeting space. For an example, see [Update a meeting space](https://developers.google.com/workspace/meet/api/guides/meeting-spaces#update-meeting-space).
- spaces
Google Meet integration, answered
- How do AI agents use Google Meet through Open Connector?
- Your user connects Google Meet once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Meet tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Google Meet MCP server?
- Yes. Open Connector can serve Google Meet as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Meet actions with credentials injected server-side.
- Where do Google Meet 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 Meet — keep the keys.
Open source, self-hostable, with Google Meet credentials that never leave your infrastructure. Run it from source today.