RoomChime for AI assistants
Ask your AI assistant to draft a poll, save it to your RoomChime workspace, open a room and summarise what the room said. RoomChime works with any assistant that supports remote MCP connectors.
What it does
RoomChime runs live audience polls. You present one question at a time, guests answer on their phones with a QR code or a six-digit code, and totals appear on the projector and your host console.
With the connector, your assistant can:
- Draft questions with RoomChime's authoring rules and save them as an event you can open and rehearse in the studio.
- Edit an event, or adapt one of RoomChime's three starter templates.
- Open a room and hand you the join code, the guest link, the projector link and a phone-control link.
- Read a room's results, summarise them, export them as CSV, end the room and delete it.
Live control stays with you. Moving to the next question, revealing results and closing answers happen on the host console or the phone-control link.
Before you start
- You need a RoomChime account. Create one at roomchime.com. The connector signs in with the same account.
- Every call stays inside your own workspace. Your assistant sees only the events and rooms you can see in the studio.
- There is no API key. The first time you use the connector, your assistant opens RoomChime's sign-in page in the browser.
- Your plan applies here as it does in the studio. Guest names, CSV export and older reports follow the same allowances.
| Server URL | https://mcp.roomchime.com/mcp |
|---|---|
| Transport | Streamable HTTP |
| Sign-in | OAuth 2.1 in your browser |
Connect
Pick your assistant. Each one asks you to sign in once.
Claude on the web, desktop and mobile
Open the link below, check the details and choose Add. Then choose Connect and sign in to RoomChime.
You can also go to Customize, then Connectors, choose Add custom
connector and paste https://mcp.roomchime.com/mcp.
On a Team or Enterprise plan, an owner adds the connector for the organization first: add RoomChime for your organization. Members then connect it from their own connector settings.
Once RoomChime is listed in Claude's connector directory, you will also be able to add it from there.
Claude Code
Add the server, then sign in from a session:
claude mcp add --transport http roomchime https://mcp.roomchime.com/mcp
Inside Claude Code, run /mcp, choose roomchime and follow
the sign-in link.
ChatGPT
Until RoomChime is listed in ChatGPT, add it in developer mode. In ChatGPT's settings, open Apps, turn on developer mode under the advanced settings, and create an app with these details:
| Name | RoomChime |
|---|---|
| URL | https://mcp.roomchime.com/mcp |
| Authentication | OAuth |
Then sign in to RoomChime. Developer mode is available on the ChatGPT plans OpenAI lists for it, and the setting names can differ slightly between plans.
Codex
The Codex CLI, app and IDE extension share one configuration. Add the server and sign in:
codex mcp add roomchime --url https://mcp.roomchime.com/mcp
codex mcp login roomchime
Or add it to ~/.codex/config.toml yourself:
[mcp_servers.roomchime]
url = "https://mcp.roomchime.com/mcp"
Cursor
Or add it to .cursor/mcp.json in a project, or
~/.cursor/mcp.json for every project:
{
"mcpServers": {
"roomchime": { "url": "https://mcp.roomchime.com/mcp" }
}
}
Cursor asks you to sign in the first time a tool runs. From the Cursor
CLI, run agent mcp login roomchime.
VS Code
Or share it with a project team through
.vscode/mcp.json:
{
"servers": {
"roomchime": { "type": "http", "url": "https://mcp.roomchime.com/mcp" }
}
}
VS Code opens the sign-in page when the server first starts.
Grok
On grok.com, open Connectors, choose New connector, then Custom. Paste
https://mcp.roomchime.com/mcp and sign in to RoomChime.
On Grok Business, an admin first adds the connector for the team at
console.x.ai.
For Grok Build in the terminal:
grok mcp add --transport http roomchime https://mcp.roomchime.com/mcp
Other clients
Any client that supports Streamable HTTP with OAuth can connect to
https://mcp.roomchime.com/mcp. A request without a token
gets a 401 that points to
https://mcp.roomchime.com/.well-known/oauth-protected-resource/mcp, which names RoomChime's sign-in service. Clients register by Client
ID Metadata Document or by Dynamic Client Registration.
Tools
Read tools never change anything. Write tools add something new. Destructive tools change or remove what exists, so most assistants ask you before they run one.
| Tool | Kind | What it does |
|---|---|---|
list_events |
read | Lists the saved events in your workspace, newest first, without their questions. |
get_event |
read | Returns one event with its questions, options, settings and revision. |
list_templates |
read | Returns RoomChime's three starter events as complete question lists. |
create_event |
write | Saves a new event as a draft you can open and rehearse in the studio. |
update_event |
destructive | Changes an event. A new question list replaces the old one, and the update is refused if the event changed since your assistant read it. |
list_runs |
read | Lists the rooms your workspace has opened, with the join code of a live one. |
get_run |
read | Returns the state of one room, how many guests joined, and its join and projector links. |
get_run_results |
read | Returns totals per question. After the room ends, it adds named answers when the event asked for names. |
get_run_closing_details |
read | Returns the emails and notes guests left after the room ended. Assistants call it only when you ask. |
export_run_csv |
read | Returns the same CSV the studio downloads. |
start_run |
write | Opens a live room and returns the join code, the guest link, the projector link and a phone-control link. |
end_run |
destructive | Ends a live room for everyone and keeps its results. |
delete_run |
destructive | Permanently deletes an ended room and everything it collected. The event itself stays. |
The draft_event prompt
Clients that show MCP prompts list draft_event. Give it
the purpose of your session, and optionally the audience and the
number of questions. It hands your assistant RoomChime's authoring
rules, asks it to show the draft for review, and saves the event with
create_event once you approve.
Example prompts
- Draft a six-question warm-up poll for a 45-minute product workshop and save it to RoomChime.
- Open a room for my Team retro event and give me the join code and projector link.
- Summarise the results of my last RoomChime run and point out the biggest split.
- Export yesterday's all-hands run as CSV.
What RoomChime receives
- Only the arguments of each tool call, such as the title and questions your assistant saves, or the id of the room it reads. RoomChime never receives your conversation, your assistant's memory or your files.
- A sign-in token that RoomChime checks on every call and does not store.
- Tool results go back to your AI client. That provider handles them under your agreement with it.
- RoomChime does not call any AI model.
The privacy policy has the details.
Troubleshooting
| What you see | What to do |
|---|---|
| Sign-in keeps coming back, or "Sign in to RoomChime" |
Remove the connector and add it again, then sign in. In Claude
Code, run /mcp and re-authenticate. In Codex, run
codex mcp login roomchime.
|
| Your events are missing | Sign in with the same account you use in the studio. Each account has its own workspace. |
| "Too many attempts" | Wait a minute, then try again. |
| "End your current live room" | A workspace runs one live room at a time. End it from the host console, or ask your assistant to end it. |
| "This event is now at revision" | The event changed after your assistant read it, for example in the studio. Ask it to read the event again and retry. |
| "Not included in this workspace's current plan" |
The same plan limits apply as in the studio. Turn guest names
off for the event, read totals with
get_run_results instead of a CSV, or open the
report in the studio.
|
| "Details are available once the run has ended" | Guests leave emails and notes only after a room ends. End the room first. |
Support
Write to support@roomchime.com with the name of your assistant and what you asked it to do. The support page covers sign-in, billing and privacy requests.