chrome-devtools-cli

Automate Chrome browser interactions by using a persistent background daemon to perform clicks, typing, and navigation. This approach handles human-like behavior for complex JavaScript web applications, enabling automated form submission and secure multi-step login flows.

Inspect network traffic and monitor console logs in real-time through runtime inspection. Evaluate JavaScript directly in the persistent Chrome environment to debug complex web applications and identify runtime performance issues during automated interactions.

Run Lighthouse audits and capture performance traces to diagnose slow page loads by automating Chrome runtime inspection. This process evaluates page rendering speed and identifies layout or performance issues within the persistent browser environment.

Yes, you need the chrome-devtools-mcp package installed locally to interface with the browser. It enables communication via Unix sockets or named pipes, which is required for the background daemon to automate Chrome interactions and debugging.

Identify interactive elements by navigating to a specific URL and taking an accessibility snapshot. This accessibility tree analysis captures the page structure within the Chrome environment to detect available interactive elements for automation.

Browser automation requires a persistent background daemon to maintain a continuous Chrome environment state. This persistent connection supports runtime debugging, allowing sequential actions like form submission followed immediately by network traffic inspection without losing context.