NEWAuto zoomZooms that feel
intentional.
Soft on glances, stronger on typing and menus — then eased like a real editor. Interest beats, not every click.
Works where Cursor & Claude already live
Cursor
Claude
MCP
Chrome
WindowsThe problem
Every demo starts from scratch.
Re-doing auto zoom 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
Auto zoom is built into the studio — not bolted on later.
01Score the beat
Dwell, approach speed, and post-click travel decide fly-bys vs feature callouts. Chrome rails get filtered out.
02Soft vs spotlight
Glance zooms stay soft. Typing and menus climb the ladder. Bias shifts the whole set — regenerate anytime.
03Merge, don’t glue
Nearby beats in the same pane become one continuous follow. Farther apart stay separate on the timeline.
In the studio
The real Screen Beaver UI — Auto zoom 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
Auto zoom lands on the timeline — export locally.
Same demo. Different finish.
Toggle auto zoom on — watch Screen Beaver do the polish work between a raw take and a shippable cut.
Studio · Auto zoom
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 auto zoom.
Free to start. Wire MCP once — then ask Cursor or Claude to film while auto zoom lands on the timeline.
