chrome-devtools
chrome-devtools is a profile-aware command-line wrapper for running Chrome DevTools MCP operations with isolated Chrome user data directories.
The tool is designed to be called as a regular CLI from agent skills. It is not registered in Hermes as an MCP server.
Design
- Profiles are explicit: every operation that targets a browser profile requires
--profile <name>. - Profiles own their Chrome user data directory and DevTools port.
- Profiles are read from
~/.config/chrome-devtools/config.toml. - If the config file is missing on startup, the CLI creates a
defaultprofile using~/.config/chrome-devtools/profiles/default. user_data_diris optional; when omitted, it defaults to~/.config/chrome-devtools/profiles/<profile-name>.- Prefer
user_data_dirvalues under~/.config/chrome-devtools/profiles/<profile-name>so Chrome profile data stays with the tool config. - The CLI may execute
chrome-devtools-mcpinternally for a selected profile. - MCP input and output are passed through without reimplementing individual Chrome DevTools tools.
- Hermes-side Chrome DevTools MCP registration is not required for this workflow.
Configuration
[[]]
= "default"
= 9222
Commands
mcp list starts or reuses the Chrome instance for the selected profile, queries tools/list, and prints the raw MCP JSON response.
mcp call starts or reuses the Chrome instance for the selected profile, then runs chrome-devtools-mcp with that profile's DevTools URL. Standard input, output, and error are inherited so MCP messages pass through the upstream process.
mcp help prints MCP-specific usage, examples, and notes about stdio JSON-RPC forwarding.
Development
This repository intentionally provides Rust through the Nix flake development shell. Do not assume cargo is installed globally.