Log inSubmit server
Pagecast logo

Pagecast

by mcpware

Record browser interactions and export them as WebM, optimized GIF, or H.264 MP4.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install Pagecast

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcpware-pagecast": {
      "command": "npx",
      "args": [
        "-y",
        "@mcpware/pagecast"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 7 tools correctly (24d ago).

Overview

mcpware/pagecast MCP server records browser pages through Playwright and lets an AI agent interact with them before exporting the result. It provides sequential actions such as scrolling, clicking, hovering, typing, navigation, and waiting, with ffmpeg-based GIF and MP4 conversion. Use it for repeatable product demos, README media, social clips, QA captures, or other browser recordings. The server runs over stdio and can launch Chromium in headed or headless mode.

Use cases

  • Record a web app demo for a GitHub README
  • Capture browser interactions for a QA report
  • Export a vertical product walkthrough for TikTok or Reels
  • Create an MP4 of a dashboard workflow
  • Regenerate demo media after a UI change

Key features

  • Playwright browser recording
  • Sequential click, type, scroll, hover, and navigation actions
  • WebM, optimized GIF, and H.264 MP4 export
  • Tooltip and cinematic zoom effects
  • Platform-based viewport presets
  • Headed and headless Chromium modes

Tools7

What Pagecast lets your agent do. Expand a tool for its parameters.

Verified live~1.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @mcpware/pagecast (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars52Stargazers on the source repository.
npm downloads663Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed7Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Pagecast works

What mcpware/pagecast does

mcpware/pagecast MCP server turns an AI-directed browser session into a recorded video. It opens a URL in Chromium, captures the page while actions are performed, and saves the session as a WebM file with an interaction timeline. The resulting recording can remain a plain screen capture or be converted into an optimized GIF or H.264 MP4.

The project fits the Browser Automation category because the recording is driven by Playwright browser actions rather than a manually operated screen recorder. It can capture clicks, typing, scrolling, hovering, key presses, selections, waits, and navigation. Cursor highlighting and click ripples are injected into the page, while tooltip and cinematic export modes can add visual focus to recorded interactions.

How it works

A typical workflow begins with record_page, which opens a URL and returns a session ID. The agent then calls interact_page with one or more actions; those actions run in sequence and are included in the recording. stop_recording closes the session and writes the WebM output plus timeline data containing interaction positions and timestamps.

For a straightforward timed capture, record_and_export or the documented record_and_gif workflow can combine recording and conversion. Separate export tools support tooltip overlays, cinematic crop-and-pan effects, GIF conversion, and MP4 conversion. Platform presets can select common dimensions such as 1280×720 for README or YouTube content, 1080×1920 for vertical short-form video, and 1080×1080 for square output.

Setup and configuration

mcpware/pagecast MCP server requires Node.js 20 or newer and ffmpeg. Install and run it with npx @mcpware/pagecast, or register it with Claude Code using its MCP command. Chromium must be installed through Playwright with npx playwright install chromium before the first recording. The default browser is visible; pass --headless when a background browser is preferred.

Recordings are written to ./recordings by default. Set RECORDING_OUTPUT_DIR to change that location. Other documented defaults include 12 FPS for GIF output, an 800-pixel GIF width, a 1.6x tooltip magnification, a 380-pixel tooltip inset, and a 2.5x cinematic zoom. The default video viewport is 1280×720, unless a platform or custom size is supplied.

Tools and capabilities

  • record_page: Start a browser recording and return a session ID.
  • interact_page: Perform recorded browser actions, including click, type, scroll, hover, press, select, wait, and navigation.
  • stop_recording: Save the active session as WebM and preserve its timeline.
  • convert_to_gif: Create an optimized GIF using ffmpeg palette processing, with configurable FPS, width, and trimming.
  • convert_to_mp4: Produce an H.264 MP4 for sharing, embedding, or social platforms.
  • smart_export: Add magnified tooltip overlays near interactions.
  • cinematic_export: Crop and pan the camera toward interaction targets.
  • list_recordings: Show WebM, GIF, and MP4 files in the output directory.

Limitations and notes

mcpware/pagecast depends on a working Chromium installation and ffmpeg, so it is not self-contained after the package is invoked. The default headed mode opens a visible browser unless headless mode is selected. Output size, frame rate, and effects affect file dimensions and processing results; GIF output is especially subject to the chosen width and FPS.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pagecast

mcpware/pagecast is an MCP server that connects AI agents to Chromium browser pages through Playwright. Its main tools record a page, perform clicks, typing, scrolling, hovering, navigation, and waits, then stop the session and export WebM recordings as optimized GIF or H.264 MP4 files.

Install it with `npx @mcpware/pagecast` and install Chromium with `npx playwright install chromium`. Node.js 20 or newer and ffmpeg are required. Claude Code can register it with `claude mcp add pagecast -- npx -y @mcpware/pagecast`.

Call `record_page` with the target URL, use `interact_page` for the browser actions, and finish with `stop_recording`. The server saves a WebM file and interaction timeline, which can then be converted to GIF or MP4.

Yes, it exports both formats. Use `convert_to_gif` for an optimized GIF or `convert_to_mp4` for H.264 video. The project also documents combined recording-and-export workflows and platform presets for common output sizes.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPagecast AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcpware-pagecast?style=directory)](https://allmcps.com/mcp/mcpware-pagecast)
HTML Embed
<a href="https://allmcps.com/mcp/mcpware-pagecast"><img src="https://allmcps.com/api/badge/mcpware-pagecast?style=directory" alt="Pagecast on AllMCPs" /></a>