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.

MeetingsOAuth 2.0MCP + RESTmeet.google.com
AUDIT LOG · GOOGLE MEETPOLICY: acme-support
09:41:07 · claude · u_8f2read
google_meet.list_recordings
List Recordings✓ allowed · 212ms
09:41:08 · claude · u_8f2read
google_meet.get_meet
Get Meet details✓ allowed · 164ms
09:41:09 · claude · u_8f2write
google_meet.create_meet
Create Google Meet Space✓ approved · approved by user
EVERY GOOGLE MEET CALL, ON THE RECORD
01 · USE CASES

What agents do in Google Meet.

01

Get a meeting's transcript

Fetch the transcript of a past Meet call to summarize action items for the team.

02

Check who attended a call

List participants from a conference record to confirm attendance for a recurring meeting.

03

End a call with confirmation

End an active conference only after the host confirms the meeting should be cut short.

02 · ACTIONS

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

12

Look things up. Allowed by default.

  • google_meet.get_meet
    Get Meet details
  • google_meet.get_transcript
    Get Transcript
  • google_meet.list_recordings
    List Recordings
  • google_meet.list_participants
    List Participants
  • google_meet.get_transcript_entry
    Get Transcript Entry
  • google_meet.get_participant_session
    Get Participant Details
  • google_meet.list_conference_records
    List Conference Records
  • google_meet.list_transcript_entries
    List Transcript Entries
  • google_meet.list_participant_sessions
    List Participant Sessions
  • google_meet.get_conference_record_by_name
    Get conference record by name
  • google_meet.get_recordings_by_conference_record_id
    Get recordings by conference record ID
  • google_meet.get_transcripts_by_conference_record_id
    Get transcripts by conference record ID

write

3

Create and change things. Allow, or ask the user first.

  • google_meet.create_meet
    Create Google Meet Space
  • google_meet.update_space
    Update Google Meet Space
  • google_meet.end_active_conference
    End active conference

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Google Meet in three steps.

  1. 01Your users connect Google MeetThey sign in to Google Meet on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, and writes like “create Google Meet Space” can wait for the user to approve.
  3. 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.
POLICY.TS
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
04 · AUTH AND DATA

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
05 · WORKS WITH

Use Google Meet from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Google Meet and Arc0, answered.

Q01

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.

Q02

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.

Q03

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.

Q04

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.

Q05

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.

Get started

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