Chrome DevTools MCP

Chrome DevTools MCP is a local stdio MCP server that lets coding agents control and inspect a live Chrome browser using Chrome DevTools and Puppeteer. It supports browser automation, debugging, performance analysis, network inspection, screenshots, Lighthouse audits, memory debugging, extension debugging, third-party developer tools, and experimental WebMCP tooling.

Installation

The upstream documentation uses npx examples with chrome-devtools-mcp@latest. For this Wardn 1.4.0 registry entry, the submitted default package launch is version-pinned to command npx and args ["-y", "[email protected]"] so the launch continues to run the reviewed package version after publication.

Requirements

Node.js LTS, npm/npx, and a current stable Chrome or newer are required. Google Chrome and Chrome for Testing are the officially supported browsers. The package engines require Node.js ^20.19.0, ^22.12.0, or >=23.

Configuration

The server supports flags for connecting to an existing Chrome instance, choosing Chrome channel/executable/profile, headless mode, viewport, proxy, network allow/block lists, tool category toggles, telemetry/update behavior, screenshot defaults, slim mode, and experimental DevTools, vision, memory, screencast, third-party, extension, and WebMCP functionality.

Privacy and Operational Notes

The server exposes the controlled browser and DevTools state to MCP clients. Performance tools can send trace URLs to the Google CrUX API unless disabled with --no-performance-crux. Usage statistics collection is enabled by default and can be disabled with --no-usage-statistics or CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS/CI. Update checks can be disabled with CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS.