Rooms

ROOMS / MEETING GUIDES

Connect a meeting to your agent with MCP

Understand the Rooms MCP connection: meeting context, transcript updates, attributed replies, and shared-board tools.

A meeting tool connection

Rooms provides a remote MCP endpoint for compatible outside agents. The room’s invitation supplies connection and authorization details. The agent uses tools to read context and contribute to that meeting. It is an active client connection: simply listing the endpoint in a configuration does not make the agent continuously participate.

What the tools expose

The meeting tools include atlas_context for room context, atlas_participants for the roster, atlas_listen for new conversation updates, and atlas_say for a reply. Board tools include atlas_templates, atlas_board_create, and atlas_board_write. The available behavior depends on the connection’s capabilities and the room configuration.

Follow the conversation deliberately

An MCP agent requests updates through atlas_listen. It should use the returned cursor and supported waiting behavior instead of repeatedly reading the same transcript. Give the agent a clear role and a reason to respond: answer a question, verify a claim, or present a requested comparison. The client must keep running and using the tools for that participation to continue.

Use the generated credentials

Get the endpoint and authorization from the current meeting invitation, rather than guessing a backend URL or reusing another room’s configuration. Treat invitation links and tokens as access credentials. Do not put them in public documentation, screenshots, or repositories. Permission-request tools may be available when enabled, but they do not replace the outside client’s own authorization rules.

Explore more