redemo

MCP

Redemo in your editor

For Claude Code and any MCP client that sends a header

Redemo speaks MCP, so the agent you already code with can drive it. Creating the demo, fetching the snippet to paste, authorising the domain it plays on, telling us you shipped — all of it from the terminal you are in, without opening a studio.

1. Get a key

In your dashboard, under Connect your agent, create a key. It is shown once — we store only a hash of it, so we cannot show it to you again. Lost it, create another and revoke the old one.

This key is secret, and that distinguishes it from the site key in your embed snippet, which is public by design and locked to your domains. This one acts as you: it can create demos on your account and change which domains your video plays on. Keep it in your environment, not in a committed file.

2. Connect

Once, for every project you work on:

claude mcp add --scope user --transport http redemo https://app.redemo.io/mcp \
  --header "Authorization: Bearer $REDEMO_MCP_TOKEN"

Pass the variable, not the value: claude mcp add echoes what you type, and a token in your scrollback is a token in your screen recording.

To share it with a repository instead, commit a .mcp.json — the variable is expanded at run time, so the file holds no secret:

{
  "mcpServers": {
    "redemo": {
      "type": "http",
      "url": "https://app.redemo.io/mcp",
      "headers": { "Authorization": "Bearer ${REDEMO_MCP_TOKEN}" }
    }
  }
}

3. Check it actually connected

Type /mcp inside a session and look for the tools, not just the server. This matters more than it sounds: claude mcp list can report ✔ Connected for a server that registered no tools at all, which looks like success and behaves like nothing being there. If the tools are listed, you are connected. If the server is listed and the tools are not, something is wrong — start with the key.

What you can ask for

You do not call these by name. You say what you want; the agent picks.

  • create_demo
    Start a demo from a product URL and a sentence about what it should show.
  • list_demos
    Every demo on your account, the stage each is at, and whose turn it is.
  • get_demo
    One demo in detail: its timeline, its latest version, where it plays.
  • get_embed_snippet
    The snippet to paste on your site, for a plain video tag or our player.
  • allow_domain
    Authorise the domain the demo will play on.
  • request_rebuild
    Ask for a re-film now, with a note about what changed.
  • watch_status
    What we last saw on your product, and when it last moved.

In practice that reads like: “Add a demo of this app to the landing page”, then later “Is the demo ready?”, then “Put it on the marketing site” — which fetches the snippet and authorises the domain in one go.

What it will not do

Approving a script, approving a finished cut and subscribing are not tools, and will not become tools. They are the three decisions that cost you something — a render is billed per scene on our side, and a published video is your product's first impression. An agent can bring you to each of them and tell you what is waiting; the yes is yours.

The rebuild ceiling applies here exactly as it does on the dashboard: asking through an agent is the same ask, counted the same way.

Other clients

Any MCP client that can send an Authorization header over HTTP will work. Connectors on claude.ai and Claude Desktop currently expect a full OAuth flow, which Redemo does not offer yet — if that is how you want to use this, tell us and it moves up the list.

When something is off

  • 401, or a connection error on startup — the key is wrong, revoked, or the variable is empty in the shell that launched your editor. Check the header is Bearer <key>, with the word.
  • Connected, no tools — see above. Restart the session: the tool list is cached hard by every client, so a restart is the reliable way to fetch it again.
  • A tool refuses — it answers in words, and the answer is the reason: a rebuild already queued, a monthly ceiling reached, a demo not live yet. The agent can usually act on it without you.
  • A key that leaked — revoke it in the dashboard. It stops working immediately, and nothing else on your account is affected.

Something missing, or a tool you wish existed? contact@redemo.io — a real person reads it.