Can Claude run Roomi for you? Everything you can do without opening the app

By Kaz Kato · Published 13 October 2026 · Updated 13 October 2026

Yes. Add the Roomi connector to Claude once, and you can do nearly everything in the app by asking. Claude deploys the demo, makes each client’s link, runs the room and the pipeline, answers comments and says who to call first. Nothing changes without your yes. It runs on your own Claude plan, so we add no AI charge.

This guide sets out each job three ways: in the app, with the command line and by asking Claude. Then it ranks the ten things most worth asking, with the exact words. Deploying from Claude is the full walkthrough, and the connector’s reference lists every tool Claude gets.

What can Claude do in Roomi for you?

Nearly everything you would open the app for. Claude can deploy a demo, rename, arrange, pause or delete a project, and make and revoke viewer links. It can read who opened the room, answer their comments and move them along the pipeline. It can also set your brand, invite your team and change your plan.

The connector gives Claude the app’s own actions as tools. It acts as you, in the one workspace you approve. Here is each job, three ways:

Job	In the app	With the CLI	Ask Claude
Put a demo live	Not in the app	roomi deploy, then roomi deploy --commit	“Deploy it to roomi”
Make the last build live again	Builds tab, Roll back to this	roomi rollback --commit	“Put the build before this one back live”
Rename or delete a project	The project’s Settings tab	Not in the CLI	“Rename the project to Ledger”
Group your projects	The Projects screen, by dragging	Not in the CLI	“Group the retail demos together, newest first”
Add or remove a page	Room tab, Pages	roomi pages add, roomi pages remove	“Add this briefing to the room as a page”
Reorder the room	Room tab, by dragging	Not in the CLI	“Put the dashboard first, then the pages”
Choose what viewers can use	Room tab, Viewer controls	Not in the CLI	“Hide the QR code in this room”
Pause the room, and resume it	Settings tab, Pause the room	Not in the CLI	“Pause the room while we fix the data”
Make a client’s link	Links tab, New link	roomi link "Priya Shah"	“Make a viewer link for Priya Shah”
Find a link they lost	Copy link beside their name	roomi link copy "Priya Shah"	“Show me Priya’s link again”
Close a link	Links tab, Revoke	Not in the CLI	“Revoke Tom’s link”
See who opened it and what they did	Activity tab	roomi links shows each link’s stage	“Who opened the demo this week?”
See where the time went	Analytics tab	Not in the CLI	“Where did people spend their time this week?”
Answer a comment, and resolve it	Feedback tab, Reply and Resolve	Not in the CLI	“Answer Priya’s comment about pricing, then resolve it”
Move someone along the pipeline	Pipeline tab, by dragging their card	Not in the CLI	“Move Priya to Yes and mark the deal won”
Keep notes on a viewer	Pipeline tab, their card	Not in the CLI	“Note that Priya wants the reporting in phase two”
Know who to call first	The project’s Overview	Not in the CLI	“Who should I call today?”
Write the follow-up	Not in the app	Not in the CLI	“Draft a follow-up to Priya from what she did”
List it on the community	Community tab	roomi community list --commit	“List the demo on the community”
Set your brand	Settings, Customisation	Not in the CLI	“Set our accent colour to this and use this logo”
Bring in a colleague	Settings, Workspace	Not in the CLI	“Invite sam@example.com to the team”
Check or change your plan	Settings, Billing	Not in the CLI	“Drop a seat from the next period”

Claude in a chat deploys a static demo held in the conversation. A demo with its own server, or one too big for a chat, goes out with the command line on your computer. The connector tells Claude when, and Claude tells you.

Ten things to ask Claude, ranked

Ranked by how much each one saves you once a demo is out. Say them as written, or in your own words: Claude picks the right tool either way.

1. “Deploy it to roomi” — the one that starts everything. Claude reads the build guide, writes the files and a guided tour, checks them and rehearses. It shows you what would go live, and publishes only on your yes.
2. “Make a viewer link for Priya Shah, expiring in two weeks” — a private link in your client’s name, on Pro. Claude gives you the address in its reply. You send it yourself.
3. “Who should I call today?” — one sentence naming the viewer to ring, with the evidence that put them first. Ask Claude to quote the evidence, so you can open the call with it.
4. “Draft a follow-up to Priya from what she did” — Claude reads her visits, how far the tour took her, her comments and her answer to what happens next. It writes a draft for you to change and send.
5. “What did Priya look at, and what did she ask?” — where her time went, screen by screen, and her questions in her own words.
6. “Answer Priya’s comment about pricing, then resolve it” — Claude shows you the answer first. On your yes, she reads it in the room, beside her comment.
7. “Move Priya to Yes, and remind me to follow up on Friday” — her card moves on the pipeline, with a reminder on the board. Nothing is sent to her.
8. “Where did people spend their time this week?” — views, people and time, day by day, and the parts of the demo that held them.
9. “Pause the room while we fix the data” — every viewer sees the room paused, with your note, until you ask Claude to resume it.
10. “List the demo on the community” — on Free, where there are no private links, this is how anyone sees it. Claude drafts the card, rehearses the listing and lists it on your yes.

Asks two to seven are about named viewers, so they need a paid plan’s private links and pipeline. On Free, Claude can still deploy, pause the room, list on the community and tell you the total views. What viewers did, and when to call turns the answers to three, four and five into a call plan.

What will Claude never do without your yes?

It never publishes, deletes, pauses or changes your team without asking. Nearly every change is rehearsed first: Claude shows you exactly what would happen, and does it only when you say yes. A yes counts for the rehearsal it answers. If anything changes afterwards, Claude rehearses again and asks again.

Behind that is one argument on the tools: commit. Without it, a tool only rehearses and changes nothing. With commit: true, it does the thing. Claude sends commit: true only after you have read the rehearsal and agreed. These rehearse first:

• Deploying, and making an earlier build live again.
• Projects: renaming one, grouping them, and deleting one, which cannot be undone.
• The room: its order, removing a page, pausing it, and what it asks of viewers.
• Feedback and the pipeline: an answer to a comment, resolving it, a stage, an outcome, a reminder and a note.
• The community: the card, the listing and taking it down.
• Your team: invitations, roles and removing someone.
• Your brand and room theme, each checked so the colours read.
• Meetings: your booking hours, and cancelling a meeting.
• Your plan: fewer seats, or a year to a month, from the next period.
• Erasing one viewer’s data, which cannot be undone.

A few act at once, so Claude asks before it uses them: making a link, revoking one (which cannot be undone) and adding a page. Each tool tells Claude whether it changes anything, and the ones that change nothing are marked read-only.

Some things stay yours, and Claude cannot do them at all:

• Sign in for you. You approve the connection yourself, in your own browser. Passkeys, sign-in methods and sessions stay in the app’s Settings.
• Make an API token. A token is a key to your account, so it is made in Settings, never in a chat.
• Pay for anything. Asked to upgrade, it makes a Stripe page for you to open and pay yourself. A change that charges your card at once is yours to confirm in the app.
• Delete your account. That is yours alone, in Settings.
• Change the team itself. Making, renaming, leaving or deleting a team, and accepting an invitation, happen in the app. Claude works in the one workspace you approved.
• Send anything to a viewer. Roomi never sends to your viewers, and Claude has no tool that does.

Is it private?

Yes. The connector acts as you, in the one workspace you approve, and holds no password or key of its own. Claude sees only what you can see in the app yourself. You can allow reading alone, and disconnect at any time. What Claude reads stays in your own conversation, under your own Claude account.

The detail, from the connector’s reference:

• One workspace, one grant. When you connect, the app asks you to approve Claude for the workspace you are in, and for nothing else.
• A short-lived pass. Claude gets a token issued for the connector alone, which lasts an hour and renews without asking you again. The platform checks each time that you still belong to the workspace.
• Read only, if you like. Allow reading alone, and any tool that changes something is refused.
• Strangers stay strangers. People at a public address are counted, never named.
• One viewer at a time. A follow-up draft reads one person’s record only, never anyone else’s on the same link, and no draft is kept.
• Their words, not orders. Claude treats a viewer’s comments as something to answer, never as instructions.
• Every showing recorded. Each time Claude shows a link’s address again, the project’s history notes it.
• Erasing on request. Ask Claude to erase one viewer’s data, and it rehearses first and then removes it for good.

The demos themselves run on mock data, and every room says so. Is it safe to send a client an AI-built app? covers the demo’s side.

Your own Claude: no AI charges from Roomi

Roomi does not run Claude for you. The connector holds no AI key. Your own Claude reads what the tools return and does the writing: the summary, the ranking in words, the follow-up draft. That runs on the Claude plan you already have, so we add no AI charge and sell no AI add-on.

That is a benefit, not a gap:

• The Claude you already use. Your own settings and the model you chose. Nothing new to learn or trust.
• No second bill. Your Roomi plan pays for the room, the links and the record. Claude’s side stays on your Claude plan.
• No hidden model. “Who should I call today?” comes from a ranking no model writes: the same evidence always gives the same sentence, in the app and in Claude.

Custom connectors work on every Claude plan, Free included; Free is limited to one. So you can start on Claude’s free plan and Free together, and pay for neither.

How do you connect Claude to Roomi?

Add it once, as a custom connector, with one address. Claude sends you to Roomi to sign in and approve it, and from then on you ask in any chat. There is nothing to install. The address is also in the app, under Settings, Connect Claude, ready to copy.

Custom connectors are on every Claude plan, and Free allows one. On Pro and Max you open Customize, then Connectors, and choose “+ Add”, then “Add custom connector”. On Team and Enterprise, an owner adds it for everyone first. You turn a connector on for a chat from the “+” button, then Connectors.

1. Add the connector in Claude, named Roomi, with this address:

   https://mcp.getroomi.com/mcp

2. Approve it. Claude opens Roomi in your browser. Sign in, read what it asks for and choose Allow.

3. Ask. In any chat with the connector on, say “deploy it to roomi”, or any of the ten above.

When is the app still the better place?

When you want to see rather than ask. A comment’s screenshot, with the pin drawn where the viewer meant, opens in the app, and so does the room as a viewer sees it. Signing in, passkeys, API tokens, deleting your account and changing the team stay there too. Everything else, Claude can do from the chat.

The app and Claude read and write the same records, so you can mix them freely. Make the link in Claude, read the comment in the app, and ask Claude for the follow-up. Buying signals a prospect is ready to talk says what to look for in either. Pricing has what each plan adds.

Start with the first ask on the list. Open the chat where you built your demo, and say “deploy it to roomi”.

Questions people ask

Do I need a paid Claude plan?

No. Custom connectors work on every Claude plan, Free included; Free is limited to one. The Roomi connector can be that one. From there, what you can do depends on your Roomi plan.

Does Roomi charge for the AI?

No. Claude does the reading and the writing on your own Claude plan. Roomi runs no model for you, holds no AI key and sells no AI add-on. Your plan with us pays for the room, the links and the record.

Can Claude send the follow-up for me?

No. Claude writes a draft from what the viewer did, and you send it yourself, by email or however you usually reach them. Roomi never sends anything to a viewer, and no draft is kept.

Can I let Claude read but never change anything?

Yes. Allow reading only when you connect. Claude can still answer every question about your projects and viewers, and any tool that changes something is refused until you reconnect and allow changes.

Does it work in Claude Code?

Yes. Claude Code adds the connector by its address, as any Claude client does. For a demo with its own server, or a build too big for a chat, Claude Code runs the roomi command line in your project instead.

Sources

• Anthropic: support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp, checked 12 October 2026

About the author

Kaz Kato, Co-founder & CTO, Roomi. Kaz co-founded Roomi with Tesh, whom he has built with since 2017: two startups that failed, one venture studio that didn’t, and an exit.