NEWBackgroundFrame the product,
not the desktop.
Padding, radius, shadow, crop, wallpaper, and motion backgrounds — compositor-style framing so every export looks intentional.
Works where Cursor & Claude already live
Cursor
Claude
MCP
Chrome
WindowsThe problem
Every demo starts from scratch.
Re-doing background by hand on every take
Opening a full editor for a thirty-second demo
Agents that capture clicks but leave the polish to you
The fix
Background is built into the studio — not bolted on later.
01Compositor math
Padding scales from the shorter frame edge so 16:9 and 9:16 cuts keep proportional breathing room.
02Look controls
Radius, shadow, wallpaper, and chrome presets turn a raw share into a product marketing still.
03Motion backgrounds
Subtle animated beds behind the framed take — atmosphere without stealing focus from the UI.
In the studio
The real Screen Beaver UI — Background selected.
Rail, inspector, stage, and timeline — the same chrome you get in the desktop app and the web demo.
Set up once & you’re done.
The only step that needs you is the first one.
01 Connect once
Install the MCP server. About thirty seconds.
$ npx @screenbeaver/mcp
02 Keep your tools
Cursor, Claude Desktop — nothing to switch.
03 Ship the demo
Background lands on the timeline — export locally.
Same demo. Different finish.
Toggle background on — watch Screen Beaver do the polish work between a raw take and a shippable cut.
Studio · Background
On
Portable. No lock-in. Local export.
On the timeline
Nudge, delete, or regenerate — nothing locked after the take.
Delete anytime
Remove markers you don’t want. Your project stays yours.
Export locallyNEW
H.264 MP4 on your machine. No cloud encode required.
One studio · every demo
Stop scrubbing for background.
Free to start. Wire MCP once — then ask Cursor or Claude to film while background lands on the timeline.
