Google Meet

Google Meet

This connector works with Google Meet through the Google Meet REST API v2 (https://meet.googleapis.com/v2): it creates meeting spaces (a Meet link), reads and changes their settings, adds co-hosts, and after a meeting reads its conference record: who joined and when, recordings, transcripts with the full spoken text, and Gemini smart notes. Everything runs as the Google account that authorized the connector.

What the API can see, and what it cannot

• google_meet_list_conference_records returns only meetings the signed-in user organised (the owner of the Calendar event or of the Meet link), newest first. Meetings the user only attended are not listed.
• A conference record exists for every call held in a space, from the moment the first person joins. Google deletes conference records, participants and transcript entries 30 days after the meeting ends. Recordings, transcript documents and smart notes stay in the organiser's Google Drive under Drive's rules.
• Recordings, transcripts and smart notes exist only if someone turned them on in that meeting (or the space has them set to start automatically) and the user's Google plan includes them. Smart notes are Gemini's "Take notes for me".
• The API cannot join a call, see chat messages, read live captions or download the video. A recording's MP4 and a transcript's Google Doc are files in the organiser's Drive: open them with the Google Drive or Google Docs connectors (driveDestination.file, docsDestination.document).
• The connector cannot list or find meetings by date in a calendar: use the Google Calendar connector for the schedule, then match its Meet link's code here with the space.meeting_code filter.

Setup (one-time, about 10 minutes)

1. Open https://console.cloud.google.com, pick or create a project, then APIs & Services → Library → enable Google Meet REST API.
2. APIs & Services → OAuth consent screen: choose Internal if you are on Google Workspace (simplest), otherwise External. For External, set the publishing status to In production: while an app is in Testing, Google revokes its refresh tokens after 7 days and the connector stops working every week. The Meet scopes are sensitive, so an External app that Google has not verified shows an "unverified app" warning; for your own use it can be clicked through (Advanced → Go to ...).
3. APIs & Services → Credentials → Create credentials → OAuth client ID → application type Web application → add the authorized redirect URI <your AnythingMCP URL>/api/mcp-oauth/callback (on AnythingMCP Cloud: https://cloud.anythingmcp.com/api/mcp-oauth/callback).
4. Paste the client ID and secret into GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET and install the connector.
5. On the connector page, click Authorize with Provider and sign in with the Google account that organises the meetings. The refresh token is stored encrypted and access tokens are renewed automatically.

One Google client for all Google connectors: the same Cloud project and OAuth client can serve every Google connector (Gmail, Google Calendar, Google Drive, Google Docs, Google Meet, Google Photos and the others). Enable each API in that project, reuse the same GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, and authorize each connector once: each one asks only for its own scopes.

Scopes: the connector asks for

• https://www.googleapis.com/auth/meetings.space.readonly: read the spaces, conference records, participants and artifacts of every meeting the user can access, including meetings created in Google Calendar.
• https://www.googleapis.com/auth/meetings.space.created: create spaces and change, end or manage members of the spaces this connector created.
• https://www.googleapis.com/auth/meetings.space.settings: change settings (access, moderation, automatic recording, transcripts and smart notes) of any space the user owns, Calendar meetings included. Automatic artifacts need this scope even on a space the connector created. For a read-only setup, keep only meetings.space.readonly in the connector's OAuth settings, authorize again, and disable google_meet_create_space, google_meet_update_space and google_meet_add_member.

Switched off at install: google_meet_end_active_conference (ends a running call for everyone) and google_meet_remove_member. Turn them on per tool if the AI should do that. Before any write, confirm with the user what will change.

Names and ids

• Conference records, participants, transcripts and recordings are passed by their full resource name as the API returns it: conferenceRecords/<id>, conferenceRecords/<id>/participants/<id>, conferenceRecords/<id>/transcripts/<id>. Copy the value; do not shorten it.
• Spaces are passed by space_id, the part after spaces/ (jQCFfuBOdN5z). google_meet_get_space also accepts the meeting code from a link (abc-mnop-xyz in https://meet.google.com/abc-mnop-xyz); updating, ending and members need the real id from the space's name.

Reading what was said in a meeting

1. google_meet_list_conference_records with filter space.meeting_code = "abc-mnop-xyz", or start_time >= "2026-10-01T00:00:00Z" (times in UTC, RFC 3339), to find the meeting.
2. google_meet_list_transcripts with its name. A transcript in state STARTED or ENDED is still being written; wait for FILE_GENERATED (usually a few minutes after the call).
3. google_meet_read_transcript with the transcript's name returns entries in spoken order: participant, startTime, endTime, languageCode and text. Up to 100 entries per call: keep calling with page_token = nextPageToken until it is missing.
4. Entries name the speaker as a participant resource; google_meet_list_participants maps those names to displayName. Entries can differ slightly from the transcript document if someone edited the document. For a summary, google_meet_list_smart_notes gives the Gemini notes document id (docsDestination.document), readable with the Google Docs connector's gdocs_get_document_text.

Creating a meeting: google_meet_create_space returns meetingUri (the link to share) and meetingCode. The space has no time or title: to put it in a calendar, create an event with the Google Calendar connector and paste the link in its description, or let Calendar add its own Meet link. config sets accessType (OPEN anyone with the link, TRUSTED people in the organisation and invited guests, RESTRICTED invited people only), moderation, and automatic artifacts {"artifactConfig": {"transcriptionConfig": {"autoTranscriptionGeneration": "ON"}}}.

Filters: conference records filter on space.meeting_code, space.name, start_time and end_time (end_time IS NULL for calls running now), participants on earliest_start_time and latest_end_time, participant sessions on start_time and end_time. Combine with AND.

Pagination: list responses carry nextPageToken while more results exist; call the same tool with the same arguments and page_token set to it.

Common errors

• 401: the authorization expired or was revoked (always after 7 days while the consent screen is in Testing). Click Authorize with Provider again.
• 403 PERMISSION_DENIED: the scope does not cover the call (changing a space this connector did not create needs meetings.space.settings; members and ending a call work only on spaces the connector created), or the user is not the organiser. 403 FEATURE_UNAVAILABLE_TO_USER: a setting such as accessType RESTRICTED that the account's plan does not offer (personal Gmail accounts). 403 "Meet REST API has not been used in project": enable the API in the Cloud project.
• 404: a wrong or shortened resource name, a conference older than 30 days, or a meeting code that expired.
• 400 INVALID_ARGUMENT: a malformed filter (strings in double quotes, times as RFC 3339 in UTC) or an unknown field in config.

Out of scope here: live events (Google Workspace Events API), the Meet Media API, Meet add-ons, downloading recordings, and calendar scheduling.