Chrome DevTools MCP: Documentation
Updated:
Connection
npx -y chrome-devtools-mcp@latest (stdio). The server launches or attaches to a local Chrome via the Chrome DevTools Protocol (built on Puppeteer). WebSocket and HTTP modes are also available for connecting to an already-running browser. No authentication required.
Tools
About 52 tools across groups:
- Input automation: clicks, form filling, hovering, drag & drop.
- Navigation: URL navigation, tabs, history.
- Emulation: CPU and network throttling, viewport size, geolocation.
- Performance: start/stop tracing, ready-made insights on bottlenecks.
- Network: request lists, details of a specific request.
- Debugging: console messages, JS evaluation, screenshots.
Agent flow
"Open the site and tell me why the homepage takes over 5 seconds to load", "check that the signup form actually sends a request to the server", "take a screenshot of the page after clicking the button".
Limits
Works with the local Chrome on the machine running the server — not a hosted service. For complex multi-browser e2e scenarios, a dedicated framework (Playwright and similar) is a better fit than this MCP alone.
Pricing
Completely free, open source, maintained by Google.