Recording by hand
Open the screen recorder, rehearse the flow, click too fast, click the wrong thing, start over. Then do it again for mobile.
Klevo · demo videos inside Claude, ChatGPT and Cursor
Klevo is an MCP server. Connect it once and "record a demo of the signup flow" comes back as an MP4: your AI clicks through the app, Klevo records it and renders a smooth cursor, zooms on the key clicks, captions and a device frame. No screen recorder, no video editor.
01The problem
The landing page, the Product Hunt post, the changelog, the onboarding email, the support doc: each wants a short clip of the app doing the thing. Each clip costs an afternoon, and the UI changes next week.
Open the screen recorder, rehearse the flow, click too fast, click the wrong thing, start over. Then do it again for mobile.
The raw recording is flat: no cursor you can follow, no zoom on the button that matters, no captions. Making it watchable means an editor and an hour.
The clip on the landing page shows last quarter's sidebar. Re-recording is the real cost, so the stale one stays up.
02How it works
Klevo connects through MCP, the standard Claude, ChatGPT and Cursor already support. Your AI drives your app one step at a time, looking at a screenshot after each click, and Klevo turns the steps into a video.
Add Klevo as a connector in Claude or ChatGPT and sign in. Cursor and Claude Code take a key. If your app has a login, save a test account as a secret: Klevo logs in before recording starts.
"Record a demo of creating a project on staging.myapp.com, desktop, 16:9." The AI opens the page, clicks and types through the flow, writes a caption for each step and finishes.
Klevo replays the steps in a clean browser and renders the cursor, zooms, captions, device frame and intro card. About a minute later the download link is in the chat. Need a vertical cut? "Render it 9:16 on a phone." No re-recording.
03What you get
The exploratory session your AI runs is never the video. Klevo replays the saved steps in a fresh browser and composes the clip from scratch, so there are no pauses, no mis-clicks and no cursor hunting for the button.
A smooth cursor on desktop, a touch ripple on mobile, an automatic zoom into the click that matters, and three styles: smooth, snappy, minimal.
Record as desktop, tablet or mobile. Export 16:9 for the landing page, 9:16 for stories and shorts, 1:1 or 4:5 for the feed. The two choices are independent.
A browser window, an iPhone, an Android phone, an iPad, or no frame at all, on a background in your brand color, with an intro and an outro card.
Your AI writes one line per step; the video shows it. On Pro, the captions become narration in the language you pick.
Save a test account, a browser session or a magic link as a secret. Klevo signs in before recording, and password fields are blurred in every frame.
If a button is gone, the render stops at that step and hands back the step number, a screenshot and the page's console errors.
Every video comes from a small JSON file: the URL, the device, a reference to the login secret and the steps with their captions. Keep it in your repo. When the UI changes, tell your AI to render it again and a fresh browser repeats the same steps on the live app. One script, every format, forever current.
Secrets are referenced by name and never written into the script. Targets are roles and labels, not pixel positions, so a moved button still gets clicked.
{
"version": 1,
"url": "https://staging.myapp.com/projects",
"device": "desktop",
"auth": { "type": "password", "secret": "DEMO_LOGIN" },
"output": { "format": "16:9", "frame": "browser", "style": "smooth" },
"steps": [
{ "action": "click", "target": "role=button[name='New project']",
"caption": "Start a new project", "zoom": true },
{ "action": "type", "target": "label=Name", "text": "Q4 launch",
"caption": "Give it a name" },
{ "action": "click", "target": "text=Save", "caption": "Done" }
]
}
04Works with
Nothing to install. Klevo is a remote connector: it works in Claude on the web, on the desktop, on your phone and in ChatGPT, and your AI, on your plan, does the driving.
Claude.ai, the desktop app, the mobile app and Claude Code. Add a custom connector and sign in.
A custom connector in ChatGPT's settings. Sign in with your Klevo account.
One block in your MCP settings file, with a key from your account.
Other AIs that support remote MCP servers connect the same way.
05Pricing
Free renders 3 videos a month at 720p with a small klevo.si mark in the corner. Pro takes the mark off, renders 1080p, reads the captions aloud and covers a launch a week.
Try it on the app you already have.
Demos that never go stale. Yearly saves $79.
Founder lifetime
For the launch only. 100 spots left at $147, then $197.
When these 100 are gone, the lifetime goes to $197. After $247 it closes for good and Pro is subscription only.
06FAQ
MCP (Model Context Protocol) is how AI assistants use outside tools. Once Klevo is connected, your assistant calls it by itself when you ask for a demo, the same way it searches the web or reads a file. You never leave the chat, and there is nothing to install.
An MP4 with a smooth cursor (or a touch ripple on mobile), an automatic zoom into the key clicks, a caption per step, a device frame and an intro card, plus a download link in the chat. The video and its script are kept in your account. Free renders at 720p, Pro at 1080p.
You save a secret once: a test account's login (email and password), a browser session exported from Playwright, or a magic link. Klevo signs in with it before recording starts, so the login never shows in the video. Use a test account, not your own.
Secrets are encrypted at rest, never shown again after saving, and sent only to the recording service for a render or a live session. They are referenced by name in scripts and never written into them. Password fields are blurred in every frame, and the usage log keeps request sizes, never what was typed.
They can't be automated, by design. The way around all three is the same: log in once in a browser, export the session (Playwright's storageState) and save it as a secret. On staging, a test-login link saved as a magic link is the most durable option.
No. Klevo's browser runs on our servers and only opens public URLs, so it needs a staging or production address it can reach. Private and local hosts are refused.
About a minute for a short demo. The AI's exploration happens live while you watch the screenshots; the video itself renders in the background, and your AI (or the Videos page) tells you when it's ready.
Yes, without recording again. Every video comes from a saved script; ask your AI to render it 9:16 for a story, 1:1 for the feed, on a phone frame, in another style, or with narration. Each render counts as a video for the month.
The render stops at that step and reports which one, with a screenshot of the page and its console errors. Either the demo needs a different target, or your app has a bug: both are useful to know. Failed renders don't count against your month.
A small klevo.si mark in the bottom-right corner of the video. Pro renders without it; after upgrading, render the script again and the clean version comes back.
50 videos a month instead of 3, 1080p without the watermark, narration from your captions, demos up to 60 steps and 3 minutes, and more saved logins. Same cursor, zooms, formats and frames as Free.
Pro forever for one payment, while the launch lasts. It starts at $147 and steps up every 100 sales, to $247; after that it closes and Pro is subscription only. Cancel a subscription any time; the lifetime has a 14-day full refund.