Release / 20 Mar 2026 / with chrome-devtools-mcp-v0.19.0, chrome-devtools-mcp-v0.20.0, chrome-devtools-mcp-v0.20.1, chrome-devtools-mcp-v0.20.2
Chrome DevTools for agents chrome-devtools-mcp-v0.20.3
Audit a web page with Lighthouse from your browser tooling.
Before you upgrade to chrome-devtools-mcp-v0.20.3 2 to fix
Use viewport strings such as `800x600x2,mobile,touch` and geolocation as `latitudexlongitude`; omit network settings to clear throttling instead of using `No emulation`.
Action required Test pages with CPU throttling, network throttling and different viewport sizes. Affects: Clients passing object-valued emulation settings or No emulation. Inferred
Read the evidence
`performance_start_trace` now defaults `reload` and `autoStop` to true when omitted.
Behavior changed Record browser performance traces and inspect performance insights. Inferred
Read the evidence
Do not combine `--categoryExtensions` with `--autoConnect`; the options are now mutually exclusive.
Action required Affects: Configurations enabling categoryExtensions and autoConnect together.
Read the evidence
What changed in chrome-devtools-mcp-v0.20.3
Lighthouse audits and an experimental `chrome-devtools` CLI are introduced; emulation parameters change format.
Install [email protected] from npm; requires Node.js and Chrome. Optional tools may require flags.
New things you can do
Available in this release.
Added Run Lighthouse audits for accessibility, best practices and SEO.
Read the evidence
Available in this release.
Added Automate and inspect Chrome from the command line without an MCP client.
Read the evidence
Available in this release.
Added Route browser actions to explicit page IDs for concurrent sessions.
Read the evidence
← chrome-devtools-mcp-v0.18.1 All Chrome DevTools for agents releases chrome-devtools-mcp-v0.21.0 → Seeded by
