sincecutoff.com
← all changes

chrome-devtools-mcp adds experimental screencast recording tools

Introduced 2026-02-25 · score 0.97

HOW TO USE IT

When recording a page during debugging, start chrome-devtools-mcp with `--experimentalScreencast` enabled and ffmpeg available on the server PATH. Call `screencast_start` with optional `path`, then `screencast_stop`; the stop response reports the saved path.

Start the MCP server with `--experimentalScreencast`, then call `screencast_start` with `{ "path": "<output>.mp4" }` and `screencast_stop` with `{}`.

WHY THIS HELPS

When recording a page during browser debugging, enable the experimental screencast tools and capture then save the recording.

REQUIREMENTS AND LIMITATIONS

  • Version: 0.18.0
  • Availability: Experimental; enabled only when the `--experimental-screencast` command line option is provided.
  • Requires Install ffmpeg and ensure it is available in the MCP server PATH.
  • --experimentalScreencast / --experimental-screencast: Boolean server option; exposes the experimental screencast tools. Default is false.
  • screencast_start.path: Output path; when omitted, a unique temporary path is generated. v0.18.0 records in MP4 format.
  • screencast_stop parameters: No parameters.
  • Prerequisite: Install ffmpeg and ensure it is available in the MCP server PATH.
  • Recording is saved in mp4 format.
  • If no `path` is provided, a temporary file with the correct extension is created.
  • Requires ffmpeg; an error is reported if ffmpeg is not installed.
  • Docs conflict: The current tool reference and current source use `filePath` and describe WebM support, while v0.18.0 source uses `path` and MP4. The v0.18.0 source was used for the version-specific tool parameters.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card