chrome-devtools-mcp exposes Chrome DevTools capabilities to coding assistants like Claude, Cursor, and Copilot in two forms: as an MCP service and via the command line. It uses Puppeteer to automate page interactions, record performance traces and provide recommendations, analyze network requests, take screenshots, and read console errors with source maps. The package includes a set of skills covering accessibility audits, cookie and login debugging, LCP optimization, memory leak troubleshooting, and connection failure handling.
Why it matters Agents can record performance traces, inspect network requests and console errors, and take screenshots, eliminating the need for manual reporting of frontend issues; it now also includes command-line tools and debugging skills.
Star count 55455 (+67 / 24h)
Reasons
- 67 new stars in the last 24 hours, total stars 55455 (indicating attention only); this column has not featured it before
- Apache-2.0 license, README clearly documents data collection and how to disable it
Usage
- Add
npx -y chrome-devtools-mcp@latestto your MCP client configuration; for Claude Code, use/plugin marketplace add ChromeDevTools/chrome-devtools-mcpto install it along with the skills
Risks
- Browser content is fully exposed to the MCP client; do not log into sensitive accounts in this browser
- Usage statistics are sent to Google by default; disable them by adding
--no-usage-statistics; performance tools may send URLs to the CrUX API