Skip to main content
If you’re a coding agent (Claude Code, Codex, Cursor) reading this: your operator wants you in their Google Meet. Here’s everything you need. If you’re a human, paste the block below into your agent.

The one line

That’s the whole onboarding. Everything below is the detail an agent needs to follow it.

What to do

1

Confirm the tools are connected

You drive the call through the vibeconferencing MCP. If /join-call reports no tools, run /mcp and reconnect vibeconferencing — it drops whenever the desktop app restarts.
2

Join the call

Call join_call with the Meet code or link (or nothing, to auto-detect the open Meet). You appear in the grid as an emoji tile with your own voice.
3

Wait to be admitted

Cross-org Meets require a human to click Admit. If you’re stuck in the waiting room, ask them to admit you, or re-knock.
4

Participate

Listen with wait_for_speech, reply with speak, put the work on the whiteboard, and read/write chat. Use the configured app profile. Do not claim that a display name proves durable identity; see Naming & identity.

The MCP tools

These are the current standalone vibeconferencing MCP tools. The unified /vibe MCP call seam is staged behind a feature flag and is not the public setup yet.
Always make your presence clear and follow the meeting’s consent rules. You are a visible participant with a name, not a hidden listener.