Connectors · Marketing & media

Google Meet MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Meet and the rest of your systems. It gives your agent 24 Google Meet actions (17 reads, 5 writes and 2 that wait for a confirmation) and holds the Google Meet credential itself, so the agent never does. It paces Google Meet's limits and records every call. Connecting Google Meet needs your own Google Meet OAuth app and one admin sign-in.

Connect Google Meet free See pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp

24actionsin one signed file
17readlook, never change
5writecreate and update
2wait for a yesdestructive, confirmed first

Set up

Connect Google Meet in three steps.

01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp
02
Connect Google Meet.
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Meet, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.
Before the first sign-in, Google Meet needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Meet app to lend you.
- access_tokenAccess token from one sign-in with your own OAuth app
- refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
- client_idGoogle OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Google Meet REST API on the…
- client_secretGoogle OAuth client secret
```
account { op: "connections.requirements", service: "google_meet" }
# free: exactly what to paste, and what is found for you
```

Make the first call. Check before a write.

Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

do    { action: "google_meet.conference_records.list" }# conference records: list · read · 1 upstream callcheck { action: "google_meet.spaces.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Google Meet at a glance

Sign-in: OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Meet, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
You provide: access_tokenrefresh_tokenclient_idclient_secret
Limits we pace to: 10 calls a second, per connection
API covered: Google Meet REST API v2 (Discovery revision 20261020)meet.googleapis.com
Built from: Google Meet's documentation, read 23 October 2026meet.googleapis.com developers.google.com
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 17 of 17 reads, for up to 2 minutes; a write clears what it affects
Shared entities: 2, so ask can line Google Meet up with your other systems
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Google Meet.

24 actions in 9 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

17readlook, never change
5writecreate and update
2destructivewait for a confirmation

Space members
6
2 read · 3 write · 1 destructive
Space members: create · Space members: list · Space members: batch update · Space members: get
Spaces
4
1 read · 2 write · 1 destructive
Spaces: create · Spaces: patch · Spaces: get · Spaces: end active conference
Conference records
2
2 read · 0 write · 0 destructive
Conference records: list · Conference records: get
Participant sessions
2
2 read · 0 write · 0 destructive
Participant sessions: list · Participant sessions: get
Participants
2
2 read · 0 write · 0 destructive
Participants: list · Participants: get
Recordings
2
2 read · 0 write · 0 destructive
Recordings: list · Recordings: get
Smart notes
2
2 read · 0 write · 0 destructive
Smart notes: list · Smart notes: get
Transcript entries
2
2 read · 0 write · 0 destructive
Transcript entries: list · Transcript entries: get

1 more area · 2 actions

Transcripts 2

Top actions

The Google Meet API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 10 of Google Meet's 10 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`google_meet.recordings.list`Recordings: list	Lists the recording resources from the conference record.	read	`comm.meeting_recording.list`11 connectors
`google_meet.conference_records.list`Conference records: list	Lists the conference records.	read	`comm.online_meeting.list`11 connectors
`google_meet.spaces.create`Spaces: create	Creates a space.	write	`comm.online_meeting.create`10 connectors
`google_meet.spaces.patch`Spaces: patch	Updates details about a meeting space.	write	`comm.online_meeting.update`11 connectors
`google_meet.recordings.get`Recordings: get	Gets a recording by recording ID.	read	`comm.meeting_recording.get`10 connectors
`google_meet.transcripts.list`Transcripts: list	Lists the set of transcripts from the conference record.	read	`comm.meeting_transcript.list`8 connectors
`google_meet.transcripts.get`Transcripts: get	Gets a transcript by transcript ID.	read	`comm.meeting_transcript.get`11 connectors
`google_meet.participants.list`Participants: list	Lists the participants in a conference record.	read	`comm.meeting_attendance.list`4 connectors
`google_meet.participants.get`Participants: get	Gets a participant by participant ID.	read	`comm.meeting_attendance.get`3 connectors
`google_meet.conference_records.get`Conference records: get	Gets a conference record by conference ID.	read	this connector
`google_meet.space_members.create`Space members: create	Creates a member.	write	this connector
`google_meet.spaces.end_active_conference`Spaces: end active conference	Ends an active conference (if there's one).	destructive	this connector

Try it

Prompts to paste into Claude.

Each one names the Google Meet actions it will call, so you know what it reads and what it changes before you send it.

Readread
Conference records: list in Google Meet and tell me what stands out.
callsgoogle_meet.conference_records.list
Writewrite
Spaces: create in Google Meet. Show me exactly what you will send before you save it.
callsgoogle_meet.spaces.create

Governance for Google Meet

Destructive actions wait for a yes.

2 Google Meet actions are destructive. These are all of them:

Spaces: end active conferencegoogle_meet.spaces.end_active_conference
Space members: deletegoogle_meet.space_members.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dogoogle_meet.space_members.deleteconfirm_policy: human

Space members: delete?

intent: the user asked me to space members: delete

run suspended · waiting for a named person · key google-meet-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "google-meet-agent",  allowed_actions: ["google_meet.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "google_meet.spaces.end_active_conference", approver: "[email protected]" },    { match: "google_meet.space_members.delete", approver: "[email protected]" }  ]}

Illustrative. Scoped to Google Meet only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Google Meet costs on actionlake.

Every Google Meet action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Meet refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

1upstream call per actionall 24 Google Meet actions
8actions pageeach page of a long list is one call
17reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Google Meet action.

24 actions by area: the id your agent calls, what it does, and its effect.

Space members6

google_meet.space_members.batch_updateSpace members: batch updatewrite
google_meet.space_members.createSpace members: createwrite
google_meet.space_members.deleteSpace members: deletedestructive
google_meet.space_members.getSpace members: getread
google_meet.space_members.listSpace members: listread
google_meet.space_members.patchSpace members: patchwrite

Spaces4

google_meet.spaces.createSpaces: createwrite
google_meet.spaces.end_active_conferenceSpaces: end active conferencedestructive
google_meet.spaces.getSpaces: getread
google_meet.spaces.patchSpaces: patchwrite

Conference records2

google_meet.conference_records.getConference records: getread
google_meet.conference_records.listConference records: listread

Participant sessions2

google_meet.participant_sessions.getParticipant sessions: getread
google_meet.participant_sessions.listParticipant sessions: listread

Participants2

google_meet.participants.getParticipants: getread
google_meet.participants.listParticipants: listread

Recordings2

google_meet.recordings.getRecordings: getread
google_meet.recordings.listRecordings: listread

Smart notes2

google_meet.smart_notes.getSmart notes: getread
google_meet.smart_notes.listSmart notes: listread

Transcript entries2

google_meet.transcript_entries.getTranscript entries: getread
google_meet.transcript_entries.listTranscript entries: listread

Transcripts2

google_meet.transcripts.getTranscripts: getread
google_meet.transcripts.listTranscripts: listread

Questions

The Google Meet MCP server, answered.

Is there a Google Meet MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 24 Google Meet actions across space members, spaces, conference records and participant sessions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Meet.

What do I need to connect Google Meet?

Your own Google Meet OAuth app, registered with Google Meet (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Meet app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "google_meet" } lists exactly what to paste.

Can an AI agent delete or change things in Google Meet?

Only if its key allows it, and only with an explicit confirmation. 2 Google Meet actions are destructive, including spaces: end active conference and space members: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Google Meet API limit?

actionlake paces every call to the limits in the Google Meet service file: 10 calls a second per connection. Repeated reads are answered from cache (17 Google Meet actions can be), which never reaches Google Meet.

What does a Google Meet action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (8 Google Meet actions page). Cache hits, searches, dry runs and calls Google Meet refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Google Meet API does it cover?

The Google Meet REST API v2 (Discovery revision 20261020) at meet.googleapis.com. It is built from Google Meet's documentation as read on 23 October 2026. 24 actions in 9 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Google Meet data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 2 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Meet credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Google Meet today.

Connect Google Meet free See pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

Google Meet MCP server for AI agents.

Connect Google Meet in three steps.

Add actionlake to Claude.

Connect Google Meet.

Make the first call. Check before a write.

What an AI agent can do in Google Meet.

Space members

Spaces

Conference records

Participant sessions

Participants

Recordings

Smart notes

Transcript entries