Google Meet to MCP: Meeting Links, Attendance and Transcripts for any AI Agent

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Google Meet, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Google Meet

Let your AI work with Google Meet: create meeting links with access, moderation and automatic recording or transcript settings, add co-hosts, and after a meeting see who joined and for how long, find its recordings and read the full transcript or Gemini notes. For meetings the signed-in user organises.

Setup

1. Open console.cloud.google.com, pick or create a project, then go to APIs & Services → Library and enable the Google Meet REST API.
2. Open APIs & Services → OAuth consent screen. Choose Internal if you are on Google Workspace (the simplest option), otherwise External. For External, set the publishing status to In production: while the app is in Testing, Google revokes its refresh tokens after 7 days and the connector stops working every week. For your own account you can click through the "unverified app" warning.
3. Open APIs & Services → Credentials → Create credentials → OAuth client ID, choose the application type Web application and add the authorized redirect URI https://cloud.anythingmcp.com/api/mcp-oauth/callback. If you host AnythingMCP yourself, enter https://your-anythingmcp-host/api/mcp-oauth/callback instead.
4. Paste the client ID into GOOGLE_CLIENT_ID and the client secret into GOOGLE_CLIENT_SECRET, then 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 Sheets, Google Docs, Google Slides, Google Forms, Google Contacts, Google Meet, Google Tasks, Search Console, Analytics and Ads. Enable each API in that project, reuse the same client ID and secret, and authorize each connector once. Each one asks only for its own permissions.

Only meetings you organised: the connector lists the calls the signed-in account organised (as owner of the Calendar event or of the Meet link), newest first. Meetings you only attended are not listed. Google deletes the call records, participant lists and transcript entries 30 days after a meeting ends. Recordings, transcript documents and Gemini notes stay in the organiser's Google Drive under Drive's rules.

Recordings, transcripts and notes: they exist only if someone turned them on in that meeting, or the meeting starts them automatically, and your Google plan includes them. Gemini notes are the "Take notes for me" feature. Once a transcript is ready, usually a few minutes after the call, the AI reads what was said entry by entry, with speaker and time. The recording's MP4 and the transcript and notes documents are files in the organiser's Drive: open them with the Google Drive and Google Docs connectors.

Creating meetings: the AI creates a Meet link with its access type, moderation and automatic recording, transcripts or Gemini notes, and can add people who join without knocking, as co-hosts if you want. A Meet link has no time or title: to put it in a calendar, use the Google Calendar connector and paste the link into the event, or let Calendar add its own Meet link. The access types are OPEN (anyone with the link), TRUSTED (people in your organisation and invited guests) and RESTRICTED (invited people only). RESTRICTED needs Google Workspace; personal Gmail accounts get the error FEATURE_UNAVAILABLE_TO_USER.

Finding a meeting: the connector cannot look up meetings by date in a calendar. Name a meeting by its Meet link or code (abc-mnop-xyz) or by when it started; the Google Calendar connector finds the event and its Meet link in your schedule. The API cannot join a call, see chat messages, read live captions or download a video.

Permissions: the connector asks for three scopes. https://www.googleapis.com/auth/meetings.space.readonly reads meeting spaces, call records, participants, recordings and transcripts, including meetings created in Google Calendar. https://www.googleapis.com/auth/meetings.space.created creates Meet links and manages the ones this connector created. https://www.googleapis.com/auth/meetings.space.settings changes access, moderation and automatic recording, transcripts and notes on any meeting you own, Calendar meetings included. The Meet scopes are sensitive, so an External app that Google has not verified shows the "unverified app" warning; for your own use, click Advanced and continue.

Read-only setup: keep only https://www.googleapis.com/auth/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, which ends a running call for everyone, and google_meet_remove_member. Turn them on one by one if the AI should do that.

Changes wait for your yes: before it creates a meeting, changes its settings or adds a member, the AI tells you what will change and waits for your confirmation.

Common errors: 401 means 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 means the scopes do not cover the call or you are not the organiser; adding members and ending a call only work on Meet links this connector created. 403 FEATURE_UNAVAILABLE_TO_USER means your plan does not offer a setting, such as RESTRICTED access on a personal Gmail account. 403 "Meet REST API has not been used in project" means the Google Meet REST API is not enabled in the Cloud project. 404 means a wrong or shortened id, a meeting older than 30 days or an expired meeting code.

The connector does not schedule calendar events, join calls, follow live events or download recordings.

Prerequisites: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET

Install the connector locally

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Open http://localhost:3000/connectors/store, pick Google Meet and paste in the env vars listed under Prerequisites.

Available tools

Example prompts

• "Who joined yesterday's call on meet.google.com/abc-mnop-xyz, and how long did each person stay?"
• "Read the transcript of my last meeting and list the decisions and the action items with their owners."
• "Create a Meet link for the board meeting that only invited people can join, with automatic transcription, and add [email protected] as co-host."
• "Find the recording and the Gemini notes of Monday's sprint review."

Next steps

• Connect to Claude
• Connect to ChatGPT