Google Meet

AllMCP gives your agent 16 Google Meet tools: create and configure meeting spaces, end a live call, see who attended and for how long, and read recordings, transcripts and Gemini notes of meetings that already happened.

All providers How connecting works

Point your client at AllMCP

Connect your MCP client to the AllMCP endpoint and authenticate with your API key.

https://go.allmcp.co/mcp/

Send your key on every request using either header:

X-API-Key: allmcp_xxx

Authorization: Bearer allmcp_xxx

If you run agents for more than one of your own customers, add ?user_id=... (and optionally ?org_id=...) to the endpoint URL so each customer’s Google connection stays separate.

Connect

Google Meet uses OAuth2, so there are no tokens to copy by hand.

Ask your agent to connect Google Meet

Tell your agent to connect the google_meet provider. It returns a secure Google sign-in link.
Grant access in your browser

Open the link, sign in to Google, and approve the requested access. That is the only manual step.

Tools by category

Once you are connected, your agent can use the tools below. You don’t need to call anything by name — just describe what you want in plain language and the agent picks the right tool.

Spaces

Create a Meet link, read or lock down a room’s settings, end a live call.

Tool	What it does
`google_meet_create_space`	Creates a meeting space and returns its `meet.google.com` join link. Every setting is optional — omit them all for a plain instant-meeting link, or set access type, entry points, moderation and its chat / reaction / screen-share restrictions, join-as-viewer, attendance reports, and auto recording, transcription and Gemini notes up front.
`google_meet_get_space`	Reads a space: its join URI, meeting code, current settings, and whether a conference is running in it right now. Accepts a space name or a meeting code from a Meet link, and can return the full raw shape including phone and SIP dial-in details.
`google_meet_update_space`	Changes a space’s settings — access, moderation and its restrictions, attendance reports, auto recording, transcription and notes. Only the settings you pass are touched; the rest are left alone.
`google_meet_end_active_conference`	Ends the conference currently running in a space, disconnecting every participant. Requires an explicit confirmation flag, and the space and its link keep working for future meetings.

Conferences

Who attended a past or live meeting, and how long each person was actually in it.

Tool	What it does
`google_meet_list_conference_records`	Lists past and ongoing conferences the connected user organized, most recent first. Narrow by space or meeting code, by a start-time window, or to conferences still running right now.
`google_meet_get_conference_record`	Returns one conference: its start and end times, the space it ran in, and the date Google auto-deletes the record.
`google_meet_list_participants`	Lists who attended — or is attending — a conference, with each person’s display name, participant type (signed-in, anonymous or phone), and overall join and leave times.
`google_meet_get_participant`	Returns one participant of a conference, in the same shape a list row uses. Useful when a participant reference arrives from somewhere else, such as a transcript entry.
`google_meet_list_participant_sessions`	Lists a participant’s per-device sessions with their join and leave times — the accurate way to total someone’s real minutes when they dropped and rejoined, or used both a laptop and a phone.

Artifacts

Recordings, transcripts and Gemini notes of a meeting that already happened.

Tool	What it does
`google_meet_list_recordings`	Lists a conference’s recordings with their state and, once the file is generated, the Drive file and a link the user can open in a browser.
`google_meet_get_recording`	Returns one recording — state, times, and its Drive file link.
`google_meet_list_transcripts`	Lists a conference’s transcripts with their state and the Google Docs file plus a browser link.
`google_meet_get_transcript`	Returns one transcript — state, times, and its Google Docs link.
`google_meet_list_transcript_entries`	Reads the transcript text itself, one entry per speech segment, in order, each with the speaking participant, the language, and start and end times. This is how an agent summarizes a meeting without any Docs or Drive access.
`google_meet_list_smart_notes`	Lists the Gemini “take notes for me” documents generated for a conference, each with its state and the notes document plus a browser link.
`google_meet_get_smart_note`	Returns one set of Gemini notes — state, times, and its Google Docs link.

Common workflows

Here are a few things you can simply ask your agent to do once Google Meet is connected.

Create a Meet link for the design review that anyone at our company can join

Who was in yesterday's standup, and how many minutes was each person actually in the call?

Summarize the Bellweather call from Tuesday from its transcript, and say who said what

Find the recording of last Thursday's pricing sync and send me the link

Restrict meet.google.com/abc-mnop-xyz to invitees only, and make chat and screen sharing host-only

Good to know

Meet spaces are rooms, not calendar events. A space is a reusable link. Putting a meeting on the calendar at a time, with invited attendees and an email invitation, is a calendar job — ask your agent to use Google Calendar for that, and Meet for the room, the live call, and everything the meeting leaves behind.
Recording, transcription and notes can only be armed in advance. Nothing can start or stop them mid-call. Your agent can turn the auto-generation settings on for a space’s future meetings; availability still depends on the Google Workspace edition, Gemini notes need Gemini licensing, and someone in the call must accept the on-screen consent prompt before anything is captured.
Artifacts take a while to appear. Transcripts commonly show up 45 minutes or more after a meeting ends, and a recording can take longer to render than the meeting itself. An empty list shortly after a call usually means “not ready yet”, not “it wasn’t recorded”.
Conference records expire after 30 days. Google auto-deletes the conference record — and the transcript text your agent reads from it — roughly 30 days after the meeting ends. The Drive recording and the Docs transcript and notes files outlive it, so fetch anything you want to keep in the days after a call, not weeks later.
Recordings and notes live in the organizer’s Drive. If you attended a meeting someone else hosted, the file link may open to access-denied and the host has to share it with you.
Meeting history covers meetings you organized. Browsing past conferences returns the ones the connected account hosted. A meeting you merely attended is still fully readable once your agent has its conference-record reference — from the organizer, or from the space while the call is live.
Meet never returns email addresses. Participants come back as display names plus a type: signed-in, anonymous, or phone. A name typed at the join screen or a partly masked phone number is not a verified identity.
Some actions are owner-only and irreversible in the moment. Only a space’s owner can change its settings or end its conference, and ending a conference disconnects everyone at once — your agent will ask you to confirm before it does.
Save the space, not the code. Meeting codes expire about a year after last use and can later be reattached to a different space, so store the space reference your agent returns rather than the short code from the link.

All providers Browse every integration AllMCP supports.

How it works One endpoint, every integration.