Clients

Warp

Warp terminal agents — MCP launch config.

Prerequisite

Install the Screen Beaver Windows desktop app first. MCP only works after the software is installed and running — the agent talks to the studio over MCP; it does not replace the app.

Get from Microsoft Store, install it, then leave Screen Beaver open while you use your agent.

MCP CLI

After the desktop app is installed, install the MCP CLI once (shared by every client):

terminalshell
npm i -g @screenbeaver/mcp

Full npm notes: npm install page.

Add Screen Beaver in Warp’s MCP / launch configuration so agent mode can call the studio.

Config

Config location: ~/.warp/launch_configurations/mcp.json (or Warp MCP UI)

mcp.jsonjson
{  "mcpServers": {    "screenbeaver": {      "command": "screenbeaver-mcp"    }  }}

Verify

Confirm Screen Beaver is running on Windows, then Start an agent session in Warp and ask it to use Screen Beaver.

Prefer outcome prompts: “Capture onboarding, add captions, generate voiceover, prepare export.” The agent should call record_and_build or live_build_demo.