Description
chrome-devtools-cli is an agent skill that teaches an agent to drive Chrome from the terminal, through the chrome-devtools command-line interface. It is for automating tasks in the browser with shell scripts or single commands, and for inspecting pages from the command line. The workflow has three steps. The agent runs a tool directly, using list_pages to find a page ID if it does not have one. It takes a snapshot of the page to get element IDs, and then acts on an element, for example with click or fill. The background server starts on its own, so the agent does not need to start, check or stop it before each use, and the browser state persists between commands. The skill includes an example snapshot that shows the element IDs the commands use. Installation is a one-time setup described in a separate reference file, and it is not part of the regular workflow. The skill is published in the chromedevtools/chrome-devtools-mcp repository, which has about 53,600 stars on GitHub. The listing shows it as free. Its security audits show a pass from Socket, and warnings from Gen Agent Trust Hub and Snyk.…
Highlights
- Drives Chrome from the terminal
- Shell scripts or single commands
- Lists pages and takes element snapshots
- Clicks and fills elements by ID
- Background server starts on its own
Ratings & Reviews
No ratings yet
Be the first to rate chrome-devtools-cli.
People also visit
chrome-devtools-cli FAQ
What is it for?
Automating browser tasks from the command line, with shell scripts or single chrome-devtools commands.
How does a typical run go?
List the pages to find a page ID, take a snapshot to get element IDs, then act on an element, such as clicking it or filling a field.
Do I need to start a server first?
No. The background server starts implicitly, and you do not need to start, check or stop it before each use.
Is the browser state kept between commands?
Yes. The state persists across commands.
Is installation covered?
Yes, in a separate reference file. Installation is a one-time setup and is not part of the regular workflow.
Is it free and checked for security?
The listing shows it as free. Its security audits show a pass from Socket, and warnings from Gen Agent Trust Hub and Snyk.
What are the best chrome-devtools-cli alternatives?
Popular alternatives to chrome-devtools-cli include chrome-devtools, qa and a11y-debugging. See all chrome-devtools-cli alternatives