chrome-devtools-mcp adds the lighthouse_audit tool
Introduced 2026-03-05 · score 0.99
HOW TO USE IT
When reviewing a page for accessibility, SEO, or best practices, call `lighthouse_audit` with `device` set to `desktop` or `mobile` and `mode` set to `navigation` to reload and audit, or `snapshot` to audit the current state.
{"device":"desktop","mode":"navigation"}{"device":"mobile","mode":"snapshot","outputDirPath":"<reports-directory>"}WHY THIS HELPS
When reviewing a page in a repository's development workflow, run an accessibility, SEO, or best-practices audit.
REQUIREMENTS AND LIMITATIONS
- Version: 0.19.0
- device: Device to emulate; allowed values: `desktop`, `mobile`.
- mode: Audit mode; `navigation` reloads and audits, `snapshot` analyzes the current state.
- outputDirPath: Directory for reports; omitted means temporary files are used.
- Performance audits are handled by existing tools.
- If `outputDirPath` is omitted, temporary files are used.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.19.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/831
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/dfdac2648e560d756a8711ad3bb1fa470be8e7c9/docs/tool-reference.md
Check the installed version and the source before using it. Entry JSON