Google Meet MCP integration

Create Google Meet Space and Update Google Meet Space both require the meetings.space.created OAuth scope, and updating a space's settings additionally needs organizer or host privileges. Rapid creation calls return HTTP 429, so Ayro backs off exponentially rather than retrying immediately.

No. Create Google Meet Space returns a standalone space with its meetingUri, meetingCode, and space name, and it does not attach to any calendar event. Linking it to an invite is a separate Google Calendar call, so Ayro hands back the join link rather than implying an invite went out.

Recordings and transcripts only exist when they were enabled during the meeting and permitted by the organizer's domain policy, and both take several minutes to process after it ends. An empty result can be temporary, so Ayro retries after a delay before concluding nothing was captured.

It can, and it asks first. End Active Conference terminates the conference in a named space and immediately drops every participant, so explicit confirmation is required before the call is made. It also only succeeds while a conference is actually live in that space.