Google Meet

@Google Meet list all conference records from the past week and show me which meetings had more than 5 participants

Found 12 conference records from the past 7 days. Here are meetings with 5+ participants: 'Q4 Planning' (March 18, 8 participants, 47 min), 'Design Review' (March 17, 6 participants, 32 min), 'All-Hands' (March 15, 14 participants, 1h 12min), 'Sprint Retro' (March 14, 7 participants, 28 min). The remaining 8 meetings had 4 or fewer participants. This data reflects completed conferences only—active or scheduled meetings won't appear here.

This example shows the MCP's ability to retrieve historical meeting data and combine it with AI reasoning to filter by attendance. Requires OAuth scope for reading conference records. Note that conference records are only created after a meeting ends, so you can't query ongoing sessions this way.

@Google Meet create a new meet space for our client demo tomorrow, make it restricted so only people with the link can join

Created a new Google Meet space with restricted access. Meeting URL: meet.google.com/abc-defg-hij. Access type set to 'TRUSTED' — only users with the direct link can join (no open enrollment). The space is persistent and can be reused for future demos. Share this link directly with your client; they won't need a Google account if you've configured external participant access in your workspace settings.

Demonstrates the MCP's ability to provision Meet spaces with specific access controls. The 'restricted' behavior depends on your Google Workspace configuration—some orgs require all participants to authenticate. Creating a space doesn't schedule a calendar event; you'd handle that separately via Google Calendar MCP.

@Google Meet get the transcript from yesterday's engineering standup and summarize the key blockers mentioned by the team

Retrieved transcript from 'Engineering Standup' (March 19, 9:15 AM, conference record ID: spaces/abc123/conferenceRecords/xyz789). Key blockers identified: (1) API rate limits on the payment provider causing checkout failures—Sarah mentioned this is blocking the release, (2) missing design specs for the mobile onboarding flow—Tom waiting on design team, (3) flaky CI tests in the auth module—Alex said it's adding 20 minutes to every deploy. The transcript is 4,200 words; full text available if you need verbatim quotes.

Shows how the MCP retrieves meeting transcripts and pairs them with AI analysis to extract actionable insights. Transcripts are only available if recording/transcription was enabled during the meeting and processing has completed (usually within an hour post-meeting). Requires OAuth scope for reading transcripts.

When Meet transcripts replace live standups for distributed teams

A 6-person engineering team spread across three time zones runs async standups by recording 2-minute video updates in Meet, then uses the transcript MCP to pull text summaries into a shared Switchy thread. The MCP's transcript-by-conference-ID tool makes this fast—no manual download or copy-paste. The trade-off: transcripts lag 10-20 minutes after the call ends, so this works for async workflows but not real-time note-taking during a live meeting. If your team already records standups or retros and you want searchable text without opening Meet's web UI every time, this MCP saves 5 minutes per person per day. Set it up once with OAuth2 and let Switchy pull transcripts automatically when someone drops a Meet link in chat.

How support leads use Meet recordings to coach reps

A 4-person customer success team at a B2B SaaS company records every onboarding call in Meet, then the team lead uses the MCP's list-conference-records and get-recordings tools to pull last week's calls into Switchy for review. The MCP filters by time range and meeting code, so the lead can isolate calls for a specific rep or customer segment without scrolling through Meet's web interface. The limitation: the MCP doesn't transcribe or summarize—it only fetches the recording file and metadata. If you need AI-generated call summaries, you'll still need a separate transcription service. But if your workflow is 'find the recording, watch the key 3 minutes, leave feedback,' this MCP cuts the retrieval step from 2 minutes to 10 seconds. Works best for teams running 10-30 recorded calls per week.

When participant session data matters for remote team accountability

A 10-person product team runs biweekly retros in Meet and the PM uses the MCP's list-participant-sessions tool to log who attended, how long they stayed, and whether they joined late. The data feeds into a Switchy dashboard that tracks engagement trends over six sprints. The MCP's participant-session endpoint gives join/leave timestamps and device type, which is enough to spot patterns like 'three people consistently drop after 20 minutes.' The catch: this only works for recorded or logged meetings—if the space wasn't set to record or the conference record wasn't created, the MCP returns nothing. If your team already records retros and you want attendance data without asking IT to pull Google Workspace admin logs, this MCP delivers it in one API call. Best for teams over 8 people where attendance drift is a real problem.