New release

Chrome DevTools MCP 1.11 records screencasts without FFmpeg

Chrome DevTools MCP 1.11.0 records browser videos without FFmpeg, lists failing Lighthouse checks in its answer, and can block file: links.

Date
Works with
Claude Code, Codex CLI, Gemini CLI

What’s new

Chrome DevTools MCP 1.11.0 came out on 15 October 2026. The screencast tools, which record a video of the browser, are now on by default and no longer need FFmpeg. The old FFmpeg recorder stays behind the `--experimentalScreencast` flag, which Google marks as deprecated.

`lighthouse_audit` now puts the failing audits and the page elements involved in its answer. The new `--no-file-navigations` flag stops the server from opening `file:` addresses. The server now also reads a config file from `~/.config/cd4a/config.json` (on Windows, `%LOCALAPPDATA%\Google\cd4a\config.json`) and reloads it when it changes. URL block and allow rules now also apply after a redirect.

Why it matters

You no longer need to install FFmpeg to record what the assistant did in the browser. Page-speed checks are quicker to act on, because the failing items arrive in the chat.

Google warns that the assistant must not be able to write the config file. A config file can change security settings, such as which Chrome program starts and which addresses are blocked.

How to try it

The install line uses @latest, so restart your assistant to get the new version. Then ask it to open a page and record a short screencast. New install: claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

Source

Checked against the source on 16 Oct 2026

All updates