cyberneticlibrary
← library

Automate Chrome browser workflows

chrome-devtools-mcpmcp_serversetup L2★0
ChromeDevTools/chrome-devtools-mcp ↗
What it does

Control Chrome browser, debug network/console, measure performance traces

Best for

Coding agents automating browser workflows, debugging network issues, and analyzing performance traces.

Inputs
  • · URL to navigate
  • · CSS selectors for click/hover/fill
  • · JavaScript code to evaluate
  • · performance trace payload
Outputs
  • · page screenshot (PNG)
  • · console messages with source-mapped stack traces
  • · network request logs (HAR-like)
  • · performance insights + CrUX real-user metrics
Requires
  • · Google Chrome or Chrome for Testing browser
  • · Puppeteer (auto-installed via npm)
Preconditions
  • · Chrome/Chromium installed
  • · Node.js LTS version
  • · Port 9222 available if using external browser
Failure modes
  • · Headless mode breaks some JS execution (window.opener, etc)
  • · Performance tracing limited to 256MB traces
  • · Sensitive data leakage in screenshots/console logs
  • · CrUX requires opt-in (default enabled, can disable with --no-performance-crux)
Trust signals
  • · Official Google ChromeDevTools project
  • · Support for Extended Stable Chrome versions
  • · CLI and MCP server modes
  • · 2446+ test passing rate
  • · Optional usage statistics (opt-out via flag)