DemoBot has an MCP server. Connect it to Claude Code or Claude Desktop and ask for a demo in plain language: the assistant plans the script from a URL, records the narrated MP4 and hands back the link, on the same account and the same credits as the web app.
Model Context Protocol · Streamable HTTP · https://mcp.getdemobot.com/
The server exposes DemoBot’s whole lifecycle as tools: map a site, plan a script, record it, fetch the video, plus presets, exports, your balance and run control. A typical demo is four tool calls, and the assistant makes them for you while you carry on with something else.
“Make a short demo of app.example.com that shows a new user creating a project.”
Sign in to DemoBot, open Account, then API keys, and create a key. Paste one of these with your key in place of YOUR_KEY. The key identifies your account, so credits, videos and refunds behave exactly as they do in the browser.
claude mcp add --transport http demobot https://mcp.getdemobot.com/ \ --header "Authorization: Bearer YOUR_KEY"
{
"mcpServers": {
"demobot": {
"type": "http",
"url": "https://mcp.getdemobot.com/",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}Everything the web app does, the tools do. A few things are worth knowing before the first call.
Scripts from 250 credits, recordings from 20, priced exactly as in the app. A new account can plan short scripts on Opus; the first credit pack unlocks longer scripts, fable and background music, through MCP as in the browser.
Planning and recording run in the background. Each tool returns an id at once and a status tool reports progress, so a long recording never blocks the conversation.
Pass the target site’s credentials with the call; they are used for that run and never stored. If the site sends a one-time code, the run pauses and a tool submits the code.
The endpoint accepts POST requests over the Streamable HTTP transport. Older SSE-only clients cannot connect to it.
Every request carries your Bearer key, and the key is shown once when you create it. Revoke it from the same page to cut a client off.
Before the first pack, an account can plan short scripts on Opus only; anything else is refused with an error, not planned on a pricier model.
Playback URLs from the video tool are fetched with the same Authorization header, or use the hosted stream link the tool returns when hosting is on.
Claude Code, with the one-line command above, and Claude Desktop or any other client that speaks Streamable HTTP and can send an Authorization header, with the JSON config. The server is a hosted endpoint, so there is nothing to install or run yourself.
No. The key resolves to your DemoBot account, so planning, recording, narration and music cost the same credits as in the web app, and failed runs are refunded the same way.
Yes. Pass the site’s credentials with the planning call: password, email code or SMS code. They are used for that run and never stored. When the site sends a one-time code, the run pauses and the assistant submits the code you give it.
Four calls. Create a script from a URL and a prompt, poll its status until it is ready, record it, then poll the video until it is complete and read the playback link. Presets, exports, balance checks and cancelling a run are tools too.
Sign up, create a key under Account, paste the command. The first credits are free, and every call after that costs what the web app charges.