NEWShortcutsKeys that show up
on screen.
Modifier chords, F-keys, and Esc recorded while you demo become keyboard shortcut overlays in the export — tutorials that teach hotkeys.
Works where Cursor & Claude already live
Cursor
Claude
MCP
Chrome
WindowsThe problem
Every demo starts from scratch.
Re-doing shortcuts 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
Shortcuts is built into the studio — not bolted on later.
01Record the chord
Modifier combinations, function keys, and Esc are captured during the take for later callouts.
02Show in the cut
Overlays teach the shortcut at the moment it happened — ideal for power-user product tours.
03Still editable
Adjust or remove overlays on the timeline if a chord was noise, not a teaching beat.
In the studio
The real Screen Beaver UI — Shortcuts 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
Shortcuts lands on the timeline — export locally.
Same demo. Different finish.
Toggle shortcuts on — watch Screen Beaver do the polish work between a raw take and a shippable cut.
Studio · Shortcuts
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 shortcuts.
Free to start. Wire MCP once — then ask Cursor or Claude to film while shortcuts lands on the timeline.
