# Listing on the Community

- URL: https://getroomi.com/docs/listing
- Built: 2026-10-26

Listing puts a demo on the Roomi Community: public at one address, behind a card strangers see. You can do all of it from Claude, from the terminal, or in the app; each way writes the same card, through the same routes, and runs the same checks. This page walks through each, Claude first.

## Before you start

- **A live build.** Listing needs a deployed demo: there has to be something to show.
- **A card.** A title of up to 60 characters and one line of up to 140, written for someone who does not know the business, and a cover: a PNG, JPEG or WebP image of at most 1 MB. A screenshot of the demo makes a good one.
- **Checked when you ask.** Asking to list checks the card and the build there and then. If they pass, the project is listed at once. If a check fails, it is not listed, and you see which part and why; change it and ask again, or ask for a review if you think the check got it wrong.
- **Checked again on every change.** Changing a listed card's words, giving it a new cover, or deploying a new build runs the checks again. It stays listed unless one fails, and a new cover shows once its own check has passed.
- **Roomi can take it off.** Roomi looks at listings the checks or reports flag, and may take one off with a comment saying why, which you read beside the card and in your notifications. Asking again after that waits for review.

Listed, the project answers to anyone at its address, with no link and no account; five people can be in it at once; on Free, its analytics are total views only. [The community](https://getroomi.com/docs/community) has the checks, the review and the public address in full.

## From Claude

With the [Roomi connector](https://getroomi.com/docs/claude) in the Claude app (desktop or mobile) or on claude.ai, ask:

```text
List the supplier portal on the Community, with the dashboard screenshot as the cover.
```

Claude drafts the card from the demo's tour and pages, shows it to you, and changes nothing until you say yes. These are the calls it makes, in order:

1. `list_projects`, to find the project's id.
2. `community_card`, to see whether it has a card and where its listing stands.
3. `set_community_card`, without `commit`: a rehearsal. It runs the pre-flight check on the project with the drafted words and says what saving would change. Claude tells you what the check found that might identify a real business or client, with neutral wording to use instead.

   ```json mcp
   {
     "projectId": "3f2b8c1e-5a47-4d9e-8b21-6c0f9e7a4d53",
     "title": "A portal for a trade supplier",
     "line": "Orders, invoices and deliveries, in one place.",
     "coverFile": "img/dashboard.png"
   }
   ```

   `coverFile` is the path of an image already in the live build, which the platform copies itself, its type read from its bytes. An image you hand Claude in the conversation goes as `cover` instead, as base64.
4. `set_community_card` again, with `"commit": true`, on your yes: the card is saved, as an unlisted draft.
5. `request_listing`, without `commit`: a rehearsal that runs the checks without writing anything and says whether the project would be listed now, would be blocked (and why), or would wait for review, with what listing means, which Claude tells you before you agree.
6. `request_listing` with `"commit": true`, on your yes: the checks run for real, and if they pass the project is listed at once, at its public address.
7. `community_card`, later, to see where it stands: listed, blocked with the reason, or taken off with Roomi's comment.

`withdraw_listing` takes it off the Community, or out of review; it rehearses first too. If a check blocked it, or Roomi took it off, and you think that is wrong, `appeal_listing` asks for a review in your words, and `list_notifications` shows the answer. After a deploy, the connector reminds Claude that the project can be listed, so on Free, where there are no viewer links, Claude offers it unprompted. [MCP tools](https://getroomi.com/docs/mcp#tools) has every argument.

## From the terminal

With the [`roomi` CLI](https://getroomi.com/docs/cli), in the project's folder. Each command rehearses and changes nothing until `--commit`:

```sh
roomi community card --title "A portal for a trade supplier" \
  --line "Orders, invoices and deliveries, in one place." --cover screenshot.png
roomi community card --title "A portal for a trade supplier" \
  --line "Orders, invoices and deliveries, in one place." --cover screenshot.png --commit
roomi community list
roomi community list --commit
roomi community status
```

`--cover` is an image on your machine; it is checked by its size and its bytes before anything is sent. `roomi community list` says whether it would be listed now, blocked or wait for review; with `--commit` it is listed at once if the checks pass. `roomi community withdraw --commit` takes it off. The Claude Code plugin's skill drives these after a deploy, and offers to write the card.

## In the app

Open the project's **Community** tab, under **Community listing**: write the title and the line, choose **Save the card**, add a cover, and choose **List on the community**. The checks run there and then, and the card's status says what they decided: **On the Community**, or **Blocked by a check** with the reason beside it and **Ask for a review**.

> [!NOTE]
> Every workspace starts on Free, and moves to Pro or Team whenever you like, in Settings, Billing. Sign in at app.getroomi.com with GitHub or Google, then add the connector to Claude at https://mcp.getroomi.com/mcp, or run the CLI with npx @getroomi/cli. These pages describe the connector, the CLI, pitch.json, the app and the room as they are.
