Can AI agents automate Chrome DevTools MCP?

Chrome DevTools MCP is automatable today through the first-party chrome-devtools-mcp server. This record is Google's Chrome DevTools for agents package that controls a live Google Chrome or Chrome for Testing instance. It is not Playwright, not Puppeteer as a product, and not a generic Chromium fork. Install with npx chrome-devtools-mcp@latest. Official docs document an MCP server plus an experimental chrome-devtools CLI. The opened tool reference lists input automation, navigation, emulation, performance traces, network inspection, console and screenshot debugging, heap-snapshot memory tools, extension tools, third-party DevTools tools, WebMCP, and Progressive Web App tools. Official browser support is Chrome and Chrome for Testing only; other Chromium browsers may work but are not guaranteed. The server can start Chrome or attach to a running instance. Usage statistics are on by default and can be disabled with --no-usage-statistics. The CLI is marked experimental, talks to a background daemon, and covers only MCP tools that take no extra arguments; --output-format=json is available. No public product REST API was established. Computer-use viability is unassessed; MCP is not a computer-use probe. MCP scores 8; the experimental CLI scores 5. MCP is the best path because official docs position it as the full agent surface over live Chrome DevTools.

Best path today: mcp · Overall automatability: 8/10