roundtable-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROUNDTABLE_CWD | No | Working directory for the room's transcript. Defaults to the current working directory. | |
| ROUNDTABLE_ROOM | Yes | The room id/name. This is the only contract shared between the two seats. | |
| ROUNDTABLE_SEAT | Yes | Which seat this server occupies: 'lead' or 'peer'. | |
| ROUNDTABLE_AGENT | No | Agent label for this seat, e.g. 'opus-5' or 'codex'. | |
| ROUNDTABLE_TOPIC | No | The topic for the room, e.g. 'Should the cache be write-through'. | |
| ROUNDTABLE_BUDGET | No | Round budget (number of lead posts). Defaults are used if not specified; e.g. 8 or 12. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| room_statusA | Where the discussion stands: whose turn it is, which round of the budget you are on, and whether the room has closed. |
| read_roomA | Read the messages posted so far. Returns everything you have not already been shown unless you pass |
| wait_for_messageA | Block until the peer posts, then return their message. Returns {"idle": true} if nothing arrives before the timeout — call it again. Returns {"closed": true} when the room is over, which is your signal to stop. This is how you stay in the conversation; do not end your turn while the room is open. |
| postA | Post to the room. Each post you make consumes one round of the budget. Use it to set the brief, push back on the peer, or ask a narrower question. |
| write_specA | Write the plan. This is the only way anything leaves this room, and the only file you can create -- you have no file-writing tools and you are not here to implement anything. Call it once you have converged, then close_room. |
| close_roomA | End the discussion. Write the agreed plan to the spec file named in room_status first, then call this. Defaults to that path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lilyanAhmetoglu/roundtable'
If you have feedback or need assistance with the MCP directory API, please join our Discord server