Summary

Meeting bookkeeping rather than meeting content — it answers who was in the room, not what was said.

The scheduling half is thin on purpose: open a space, change its access setting, end it. The attendance half is where it earns a place — conference records break down to individual participants and then to each continuous join-and-leave interval, which is what you need to reconstruct a meeting after the fact. The tool list stops there; nothing in it reaches transcripts, recordings or chat.

What it is

A hosted MCP server over the Google Meet API. One half creates, updates and ends meeting spaces; the other half reads the conference records those meetings leave behind, down to each participant and each stretch of time they were connected.

What you get

Create a meeting space and get its join link back
Read a space's current details, including its access setting
Change a space's configuration — for instance who is allowed to join
End an active space, which disconnects everyone in it
List past conference records for the connected account, or fetch one by name
List the participants on a conference record, or read one participant's details
Read each continuous join-and-leave interval a participant had, singly or as a list
Page through and filter record and participant lists using the Meet API's own filter expressions

Requirements

Reached as a hosted endpoint on MewCP rather than started on your machine. You connect a Google account over OAuth in the MewCP dashboard, and that credential has to carry the Meet permissions for whatever the agent calls. Usage draws on the credits in the account.