NEWSoundsClicks, whooshes,
and music beds.
Insert click, whoosh, and typing SFX on the timeline — then add a music bed with ducking under voiceover when you narrate.
Works where Cursor & Claude already live
Cursor
Claude
MCP
Chrome
WindowsThe problem
Every demo starts from scratch.
Re-doing sounds 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
Sounds is built into the studio — not bolted on later.
01Insert SFX
Plant click, right-click, whoosh, and typing sounds where the UI deserves tactile feedback.
02Music bed
Import audio or pull helper tracks — keep energy under the demo without drowning the product.
03Duck for voice
When AI VO or mic narration is present, music can sit underneath so words stay readable.
In the studio
The real Screen Beaver UI — Sounds 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
Sounds lands on the timeline — export locally.
Same demo. Different finish.
Toggle sounds on — watch Screen Beaver do the polish work between a raw take and a shippable cut.
Studio · Sounds
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 sounds.
Free to start. Wire MCP once — then ask Cursor or Claude to film while sounds lands on the timeline.
