Do it all from Claude
You don’t have to use the app. Ask Claude to use it for you.
Deploy, send, follow up and run your team from the chat you built it in.
Roomi is built to be run from Claude. Add the connector to your own Claude once and sign in. Then say what you want: deploy a demo, make each person a link, list it on the community, or ask who’s interested. Anything that changes something rehearses first or asks you. Your Claude plan covers Claude’s work.
Connect it in three steps
Once, in the Claude you already use: claude.ai, the Claude app or Claude Code. There’s nothing to install.
- Step one
Add the connector
In Claude, open Customize, then Connectors. Choose “+ Add”, then “Add custom connector”. Name it Roomi and paste the address https://mcp.getroomi.com/mcp. On a Team or Enterprise plan, an owner adds it for everyone first, and each person then connects it.
- Step two
Sign in and allow it
Claude sends you to Roomi in your browser. Sign in, check what Claude may do, and choose Allow. The grant is for that one workspace.
- Step three
Say “deploy it to roomi”
In the chat where you built it. Claude checks the files, writes the tour with you, rehearses, and asks before anything goes live.
deploy it to roomimake a link for Priya at Acmewho’s warmest this week, and why?
Everything you can ask Claude to do
Each line is something the connector does today, grouped by what it is about. Anything that changes something rehearses first or asks you first. 56 things to ask, done by 100 of the connector’s tools. The last column says whether each one changes anything.
- Changes something, and only on your yes
- Only reads
| What you’d say | What happens | Changes anything |
|---|---|---|
| Deploying | ||
| “Deploy this demo to Roomi.” | Claude reads the build guide, checks every file, writes the tour with you and rehearses. You see what would go live, and it publishes on your yes. | YesYes, once you say so |
| “Send this as a preview first, so only my team sees it.” | The build goes to a preview that only your team sees, while viewers keep the live one. It goes live, or the preview ends, on your yes. | YesYes, once you say so |
| “Roll back to yesterday’s build.” | The build before the live one, or the one you name, goes live again on your yes. | YesYes, once you say so |
| “What’s live, and what did we deploy last week?” | The live build and every build before it: who deployed it, when, and each time it went live. | NoNo, it only reads |
| “The demo is erroring: read its logs.” | What the running copies of a container demo are writing, with secrets taken out. | NoNo, it only reads |
| Viewer links | ||
| “Make a link for Priya, expiring in two weeks.” | A private link with her name on it, on Pro and up. Claude shows it to you once, and you send it however you usually reach her. | YesYes, once you say so |
| “Priya lost her link: get it to her again.” | Her link’s address again, for you to resend, and each showing is recorded. If it has gone astray, it gets a new address on your yes. | YesYes, once you say so |
| “Revoke Sam’s link.” | The link stops opening the room at once. It can’t be undone. | YesYes, once you say so |
| “Nora asked us to delete what she did: erase it.” | Claude shows what would go: a whole link, or one person under it. It goes on your yes, and can’t be undone. | YesYes, once you say so |
| What viewers did | ||
| “Who opened the room, and what did they look at?” | Each link and its visits: who opened the room, when, and the time on each screen and page. | NoNo, it only reads |
| “Who’s hottest right now, and who hasn’t opened their link?” | Who’s leaning in, with the evidence: return visits, time inside, questions. Who hasn’t opened yet, and who is in the room right now. | NoNo, it only reads |
| “Where did people spend their time this week?” | Views, people and time, day by day, and the time spent on each part of the demo. | NoNo, it only reads |
| “Did the new build hold people longer than the last one?” | Visits, time inside and comments for each build while it was live, newest first, so you can see whether a fix worked. | NoNo, it only reads |
| “Write Priya a follow-up from what she looked at.” | Claude reads exactly what she did and writes from that alone, for you to send. | NoNo, it only reads |
| Feedback | ||
| “What did viewers say?” | Each viewer’s answer to “What happens next?”, and their comments in their own words, with the conversation since. | NoNo, it only reads |
| “Answer Priya’s comment about pricing, then resolve it.” | Your answer appears beside her comment in the room, on your yes. Resolving it changes nothing she sees. | YesYes, once you say so |
| The pipeline | ||
| “Show me the pipeline.” | Everyone on the board: each person’s stage, the outcome you marked, when to follow them up, and the evidence. | NoNo, it only reads |
| “Move Priya to Yes and mark the deal won.” | Her card moves to the stage you name, and the deal is marked won, lost or later. The evidence’s own reading stays beside it. | YesYes, once you say so |
| “Remind me to follow up with Sam on Friday.” | A reminder on the board, with a line on what it is about. Nothing is sent to anyone. | YesYes, once you say so |
| “Note that Priya wants the reporting in phase two.” | A note on her card, for your team alone. Viewers never see it. | YesYes, once you say so |
| The room | ||
| “Add our pricing page to the room.” | A page beside the demo, in Markdown or HTML, for every viewer at once. Claude can take a page away again. | YesYes, once you say so |
| “Put the brochure PDF in the room.” | A PDF or an image in the room, after the pages, shown in the room’s own reader. | YesYes, once you say so |
| “Put the dashboard first, then the pages.” | The room’s apps, pages and files in the order you give. Claude shows the new order first, and every viewer sees it on your yes. | YesYes, once you say so |
| “Hide the QR code and the reactions in this room.” | Each control the room offers its viewers, on or off. A control that is off is not drawn. | YesYes, once you say so |
| “Pause the room while we fix the data.” | Every viewer sees the room paused, with your note if you give one, until you ask Claude to resume it. | YesYes, once you say so |
| “Offer ‘Book a meeting’ and ‘Ask a question’ as the next steps.” | What the room offers under “What happens next?”, in your order and your words. | YesYes, once you say so |
| “Ask viewers for their email before they see anything.” | Every private link of the project asks for the viewer’s email first, or stops asking. | YesYes, once you say so |
| “What does the tour show, step by step?” | Each step of the guided tour, what it puts on the stage, and how its rehearsal went at deploy. | NoNo, it only reads |
| “Who paused the room last week, and who was sent a link again?” | What happened to the room, newest first: each pause, each link shown again or given a new address, and who did it. | NoNo, it only reads |
| “Is the room turning anyone away?” | Whether a rush has paused new visitors at the public address, and how many visitors the room turned away this month. | NoNo, it only reads |
| Meetings | ||
| “What meetings are coming up?” | The meetings viewers booked in your rooms that are still to come, and how “Book a meeting” books. | NoNo, it only reads |
| “Offer meetings on Tuesday and Thursday afternoons.” | “Book a meeting” books from your weekly hours in the room, or sends viewers to your own booking page. | YesYes, once you say so |
| “Cancel tomorrow’s meeting with Sam.” | Claude names the meeting, and it is cancelled on your yes. | YesYes, once you say so |
| The community | ||
| “List this demo on the community.” | Claude writes the card, flags anything that might name a real client, and lists it once the checks pass. | YesYes, once you say so |
| “Take it off the community.” | Off on your yes, with the card kept as a draft. | YesYes, once you say so |
| “Ask Roomi to look at the block on my listing again.” | A request to review the block, with your reason, for the Roomi team to decide. | YesYes, once you say so |
| “Anything new? Then mark it all read.” | Your notices: a listing taken off, a project taken down, a review decided. Then every one marked read. | YesYes, once you say so |
| Projects | ||
| “List my projects.” | Every project in the workspace, by name and address. | NoNo, it only reads |
| “Rename the project to ‘Ledger’.” | The name the room and the app show. Its address and every viewer link stay as they are. | YesYes, once you say so |
| “Delete the old test project.” | Claude says what would go. On your yes, with its address as you would type it, every link stops opening the room. It can’t be undone. | YesYes, once you say so |
| “Group the retail demos together, newest first.” | Your projects in groups, in the order you give, as the Projects screen shows them. Deleting a group deletes no project. | YesYes, once you say so |
| Brand and theme | ||
| “Make the room ours: our name, our logo and our green.” | Claude checks the colour reads well, then sets your name, colour and logo for every room. | YesYes, once you say so |
| “Give the room rounder corners and a serif for headings.” | Every colour of the room, its corners and its typeface, each colour checked so it stays readable. Shown on Team. | YesYes, once you say so |
| Teams | ||
| “Who’s on the team, and who is still invited?” | Your workspaces, the people in each and their roles, and the invitations still waiting. | NoNo, it only reads |
| “Invite sam@example.com to the team.” | Claude shows the invitation, then gives you its link to send. It can cancel one too. | YesYes, once you say so |
| “Make Tesh an owner.” | A new role for someone in the team, or taking them off it. | YesYes, once you say so |
| Plan and billing | ||
| “What plan are we on, and how much have we used?” | Your plan, how it’s billed, what you’ve used, anything owed, and every invoice and receipt. | NoNo, it only reads |
| “I want Pro, billed yearly: give me the page to pay.” | A Stripe page for you to open and pay on yourself. Claude pays for nothing. | YesYes, once you say so |
| “Drop a seat from the next period.” | Fewer seats, or a year to a month, from the next period, on your yes. A change that charges your card now is yours to confirm in the app. | YesYes, once you say so |
| “I need to update my card, and get last month’s receipt.” | A Stripe page to change your card or cancel, and a fresh link to an invoice’s PDF. You open each one yourself. | YesYes, once you say so |
| “We missed a payment: what are our options?” | What moving to Free would pause, which can’t be undone. Once what’s owed is paid, a Stripe page to buy back the plan you had. | YesYes, once you say so |
| You | ||
| “I’m new: what’s left to set up?” | What you’ve done and what’s left: a first demo live, shared, and a first visit. Claude takes you through the rest a step at a time. | YesYes, once you say so |
| “Call me Kaz, and use this photo.” | The name and photo your team and your rooms show for you. | YesYes, once you say so |
| “Set my community handle and a line about me.” | Your handle and a line about you, which anyone who opens your profile from a listing sees. | YesYes, once you say so |
| Notifications and notes | ||
| “Stop telling me every time someone opens a link.” | Which kinds of notice you get, one kind at a time. Sign-in, security and billing messages can’t be turned off. | YesYes, once you say so |
| “Tell the Roomi team the pipeline needs a filter.” | Your note goes to the Roomi team. Claude reads you their replies, and answers them for you. | YesYes, once you say so |
What Claude never does without your yes
The tools themselves hold Claude to these. Each one that changes something says so, and the ones that matter rehearse first.
Publish a demo
A deploy rehearses and shows you what would go live. It goes live on your yes to that rehearsal, and a yes never carries over once anything changes.
Change your team, brand or listing
Each one rehearses first and shows you the change. Links and pages are marked as changes, so Claude asks before making one.
Sign in or pay for you
Signing in happens in your browser. A plan change is a Stripe page you open yourself: Claude never opens it or enters a card.
Send anything to your viewers
Roomi sends nothing to them. Claude hands you each link, and you send it however you usually reach people.
Claude sees what you ask for, and nothing else
It works from your own workspace, as you, when you ask.
- It acts as you, on the one workspace you approve when you connect it.
- It reads only what a tool returns, when you ask. Nothing flows to Claude in the background.
- Roomi receives the tool calls Claude makes, never your conversation.
- Allow reading only, and every change is refused until you reconnect and allow it.
- The screenshots pinned to viewers’ comments stay in the app. Claude is told where a comment was left, never given the picture’s address.
- Disconnect it in Claude whenever you like. The links you made stay as they are.
your own Claude
Your own Claude, so no AI charges from Roomi
You connect the Claude you already pay for. Roomi doesn’t run Claude for you, on its account or anyone else’s.
No AI charges from Roomi
Your own Claude plan covers what Claude does. Roomi’s plans cost the same whether you use Claude or not.
Your own context
Claude already knows what you built, who it’s for and how you write. It brings that to every deploy, link and answer.
The Claude you already use
claude.ai, the Claude app on desktop and phone, or Claude Code in your repository. Nothing new to learn.
Claude, the app or the command line
All three reach the same rooms, links and analytics. Here they are ranked for most of what you’ll do.
- Ask Claude — the quickest for nearly everything. One sentence deploys, sends, lists or answers, in the chat you built it in, with a rehearsal before any change.
- The Roomi app — the best for seeing it all at once: the dashboard, each person’s journey and the pipeline, drawn for you. You sign up and approve Claude there too.
- The command line (CLI) — for a demo with a server, a build bigger than a chat carries, or work in a repository. Claude Code runs it for you.
Questions
- Do I still need the Roomi app?
- Only for what you’d rather see than ask. You sign up and approve Claude in the app, in your browser. After that, Claude can deploy, make links, read what viewers did and answer them. It can run the room, the pipeline, the community, your team and your plan for you. The app shows the same things at a glance.
- Does Roomi charge for Claude?
- No. You connect your own Claude, and your own Claude plan covers what it does. Roomi doesn’t run Claude for you, and adds no AI charges. Free costs nothing, and Pro is £4 a month before VAT, with Claude or without it.
- Which Claude plans work?
- Custom connectors work on every Claude plan, Free included; Free is limited to one. Roomi needs only the one.
- What does Claude see of my workspace?
- Only what a tool returns when you ask: your projects, links, visits and feedback, in the one workspace you approved. Roomi receives the tool calls Claude makes, never your conversation.
- Can Claude publish or change something without me?
- No. Nearly every change rehearses first, and happens only on your yes to that rehearsal. Making or revoking a link and adding a page are marked as changes, so Claude asks before each one.
- Can I deploy a demo with a server from Claude?
- Yes, from Claude Code: Claude runs the CLI on your machine, which builds the container and rehearses it. In a chat on claude.ai or in the Claude app, the connector deploys a static demo, and says when the CLI is the better route.
- Do my viewers need Claude, or an account?
- No. They open their link in any browser, with nothing to sign up for. Claude is how you run Roomi; your viewers never meet it.
how we checked
Fair, and dated
Every claim about another product on this page is from that product’s own pages, each read on the day beside it, the oldest on 12 October 2026. Roomi is ours, and says so. If something here is out of date, tell us and we’ll fix it the same week.
- Claude, read 12 October 2026support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp
Your next deal is one sentence away.
Start free, connect your own Claude, and say “deploy it to roomi”.