Chrome DevTools MCP lets coding agents record video without ffmpeg

A coding agent can now record what happens in Chrome without a separate ffmpeg installation. Chrome DevTools MCP 1.11.0, released October 15, enables its built-in screencast tools by default. The versioned configuration describes the older ffmpeg implementation as a deprecated alternative, rather than a requirement for the new recording path.

The server connects a compatible agent to a live Chrome browser for automation, screenshots, network inspection and performance work. Recording gives an agent workflow a video artifact alongside individual screenshots; the tool reference exposes screencast_start and screencast_stop. AITrending reviewed the shipped documentation and release notes but has not run a recording test.

Browser debugging gains more controls

The release also adds analyze_heapsnapshot_contexts, pagination and name-length controls for heap comparisons, and an ignoreCache option for performance tracing. Its Lighthouse tool can return failing audits and DOM nodes inline. These are debugging capabilities in an MCP server and CLI, not a new underlying language model.

The documented setup adds npx with arguments -y and chrome-devtools-mcp@latest to an MCP client’s configuration. To select this release explicitly, the package can be pinned to chrome-devtools-mcp@1.11.0. The project requires npm and Chrome, recommends Node.js LTS, and its package accepts Node 20.19+, 22.12+ or 23+. It officially supports Google Chrome and Chrome for Testing; compatibility with other Chromium browsers is not guaranteed.

The setup does not specify a model-provider API key for the MCP server itself. Any coding-agent subscription or model-provider charges belong to the connected client and its provider.

The new file switch is not confinement

Version 1.11.0 adds --file-navigations=false to reject file: navigations performed by its page tools, including matching view-source: targets. The default is still true, so upgrading does not automatically turn this restriction on.

The configuration explicitly says this is not a filesystem sandbox: it does not cover pages already open when the server connects, and the browser can reach the filesystem by other means. The README also warns that MCP clients can inspect and modify data in the connected browser. Operators should choose browser sessions and permissions accordingly.

Usage statistics remain enabled by default, with --no-usage-statistics as the opt-out. Performance tools may send trace URLs to Google’s CrUX API unless --no-performance-crux is set. Chrome’s own metrics preference does not control this server’s usage-statistics setting.