Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.

The chrome devtools mcp CLI lets you interact with the browser from your terminal. Setup Note: If this is your very first time using the CLI, see [references/installation.md](references/installation.md) for setup. Installation is a one time prerequisite and is not part of the regular AI workflow. AI Workflow 1. Execute : Run tools directly. If you don't know the target page's ID, run chrome devtools list pages to find it. The background server starts implicitly; do not run start / status / stop before each use. 2. Inspect : Use chrome devtools take snapshot <pageId to get an element <uid . 3. Act : Use chrome devtools click <pageId <uid , chrome devtools fill <pageId <uid <value , etc. State persists across commands. Snapshot example: Permissions & File Access By default, the CLI has full filesystem access ( allowUnrestrictedPaths=true ), allowing file saving parameters ( filePath , outputDirPath ) and upload file to access files anywhere on the system. Pass allowUnrestrictedPaths=false if you want to restrict file access to the OS temp directory. Command Usage Required arguments are passed positionally; optional arguments use flags. Use help on any command for usage details. Output defaults to plain Markdown like text; pass output format=json for JSON. Input Automation (<uid from snapshot) Navigation Emulation Performance Memory Memory Debugging (requires memoryDebugging=true ) Network Debugging & Inspection Extensions Progressive Web Apps (requires categoryPwa=true ) Experimental Features Experimental tools are disabled by default. Enable them with the corresponding flag during start . Service Management

chrome-devtools-cli