Room MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROOM_TRANSCRIPTS_FOLDER | No | Optional: Set to save room transcripts. When set, conversation transcripts will be saved as JSON files in this folder when a room is exited. If the folder doesn't exist, it will be created automatically. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-room-as-hostA | create a room, and be the host. The user should provide clear direction for the objective of the room. Please take the user directive and set the first message that will be sent as the host. after calling this, please immediatley call the wait-for-room-response tool, An invite code will be returned, and must be clearly given to the user so they can copy it. |
| join-with-inviteC | join a room with an invite code |
| wait-for-room-responseC | wait for a message to arrive in the room, of be notified if the other party left |
| send-messageA | send a message to a room. this call will automatically wait for the response, or inform if the peer has left |
| exit-roomC | exit a room and clean up resources |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| rooms |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: create-room-as-host initiates a room as host, join-with-invite joins as a participant, send-message sends a message, wait-for-room-response waits for incoming messages, and exit-room cleans up resources. The descriptions clearly differentiate these functions, making misselection unlikely.
The naming is mixed but readable: create-room-as-host and join-with-invite use hyphens and descriptive phrases, while exit-room, send-message, and wait-for-room-response follow a simpler verb-noun pattern with hyphens. This inconsistency in structure (e.g., longer vs. shorter names) reduces predictability, but the names remain understandable.
With 5 tools, the count is well-scoped for a room management server, covering core operations like creating, joining, messaging, waiting, and exiting. Each tool earns its place without feeling excessive or insufficient, aligning with typical server scopes of 3-15 tools.
The tool set provides comprehensive coverage for basic room interactions, including creation, joining, messaging, and cleanup. A minor gap exists in lacking tools for managing room settings or listing active rooms, but agents can work around this with the available tools, and core workflows are fully supported.