Record any browser page as GIF or video via MCP
Most browser automation work still happens through a UI a human drives. Pagecast MCP server moves it into the conversation instead. Record any browser page as GIF or video via MCP.
Tell your AI to demo your app. Pagecast records the browser, tracks every click and keystroke, and exports a shipping-ready GIF or MP4 — with tooltip zoom overlays and cinematic pan effects. No screen recorder. No video editor. No post-production. Make a demo gif automatically after every PR if you want.
The server publishes 9 tools. What each one is for:
record_page — Open a URL, start recording. Auto-injects cursor highlight + click rippleinteract_page — scroll, click, hover, type, press keys, select, navigate, waitForSelector — all captured with bounding boxesstop_recording — Stop and save .webm + -timeline.json (event timeline with interaction positions)smart_export — Tooltip overlay — magnified tooltip close-up on each interactioncinematic_export — Cinematic crop-pan — camera follows the action between interaction targetsconvert_to_gif — WebM → optimized GIF (ffmpeg two-pass palette, configurable FPS/width/trim)convert_to_mp4 — WebM → MP4 (H.264, ready for social/sharing/embedding)record_and_export — All-in-one: record → auto-export to GIF or MP4 based on platformlist_recordings — List all .webm, .gif, and .mp4 files in output directoryInstallation goes through your MCP client rather than a global install: point it at @mcpware/pagecast on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pagecast's toolset — record_page, interact_page, stop_recording and 6 more — is a fair guide to whether it matches your workflow. It is maintained by mcpware; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Pagecast's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| record_page | Open a URL, start recording. Auto-injects cursor highlight + click ripple |
| interact_page | scroll, click, hover, type, press keys, select, navigate, waitForSelector — all captured with bounding boxes |
| stop_recording | Stop and save .webm + -timeline.json (event timeline with interaction positions) |
| smart_export | **Tooltip overlay** — magnified tooltip close-up on each interaction |
| cinematic_export | **Cinematic crop-pan** — camera follows the action between interaction targets |
| convert_to_gif | WebM → optimized GIF (ffmpeg two-pass palette, configurable FPS/width/trim) |
| convert_to_mp4 | WebM → MP4 (H.264, ready for social/sharing/embedding) |
| record_and_export | All-in-one: record → auto-export to GIF or MP4 based on platform |
| list_recordings | List all .webm, .gif, and .mp4 files in output directory |
{
"mcpServers": {
"pagecast": {
"command": "npx",
"args": ["-y", "@mcpware/pagecast"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.