Google Meet for AI agents
Google Meet is Google's video conferencing tool for meetings, screen sharing, and recorded calls within Workspace. Teams rely on it to keep a record of what was discussed and decided. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Google Meet.
Get a meeting's transcript
Fetch the transcript of a past Meet call to summarize action items for the team.
Check who attended a call
List participants from a conference record to confirm attendance for a recurring meeting.
End a call with confirmation
End an active conference only after the host confirms the meeting should be cut short.
15 Google Meet actions, graded by risk.
Every Google Meet action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
12Look things up. Allowed by default.
- google_meet.get_meetGet Meet details
- google_meet.get_transcriptGet Transcript
- google_meet.list_recordingsList Recordings
- google_meet.list_participantsList Participants
- google_meet.get_transcript_entryGet Transcript Entry
- google_meet.get_participant_sessionGet Participant Details
- google_meet.list_conference_recordsList Conference Records
- google_meet.list_transcript_entriesList Transcript Entries
- google_meet.list_participant_sessionsList Participant Sessions
- google_meet.get_conference_record_by_nameGet conference record by name
- google_meet.get_recordings_by_conference_record_idGet recordings by conference record ID
- google_meet.get_transcripts_by_conference_record_idGet transcripts by conference record ID
write
3Create and change things. Allow, or ask the user first.
- google_meet.create_meetCreate Google Meet Space
- google_meet.update_spaceUpdate Google Meet Space
- google_meet.end_active_conferenceEnd active conference
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Google Meet in three steps.
- 01Your users connect Google MeetThey sign in to Google Meet on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, and writes like “create Google Meet Space” can wait for the user to approve.
- 03Any agent can actYour agent calls Google Meet through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('google_meet', { read: 'allow', write: 'ask', // create_meet destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Google Meet connects.
Users sign in to Google Meet on Arc0 Connect and approve the scopes you request. Build with Arc0’s Google Meet OAuth app, or bring your own so the Google Meet consent screen names you. Tokens refresh automatically, and you can export them whenever you want.
The same Google Meet connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- OAuth 2.0
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Google Meet from any agent.
Google Meet and Arc0, answered.
Can I use Google Meet with Claude, ChatGPT or Cursor?
Yes. Connect Google Meet to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Google Meet actions you allow.
How do users connect Google Meet?
Users sign in to Google Meet on Arc0 Connect and approve the scopes you request. Build with Arc0’s Google Meet OAuth app, or bring your own so the Google Meet consent screen names you. Tokens refresh automatically, and you can export them whenever you want.
Which Google Meet actions can my agent take?
15 in total: 12 read, 3 write and 0 destructive, such as “create Google Meet Space”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Google Meet?
Yes. Allow read actions and deny writes in the Google Meet policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Google Meet too?
Yes. The same Google Meet connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Google Meet into your agent.
Your users connect Google Meet once, under your brand. Your agent gets 15 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan