Chrome DevTools for agents
Lets coding agents control and inspect a live Chrome browser via MCP or CLI.
Tested on Linux
Use it
Linux x86_64
You need first
- Runtimes:
Node.js LTS version,npm - System packages:
Chrome current stable version or newer
npm global install chrome-devtools-mcp
npm i chrome-devtools-mcp@latest -g && chrome-devtools-mcp --help
Check that it works
chrome-devtools-mcp --helpThe output should contain “Print CLI options”.
Add it to your agent
claude mcp add chrome-devtools-mcp -- chrome-devtools-mcp --headless --no-sandbox --isolatedJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"chrome-devtools-mcp": {
"command": "chrome-devtools-mcp",
"args": [
"--headless",
"--no-sandbox",
"--isolated"
]
}
}
}What it does
- Record traces and extract performance insightsNot tested
- Analyze network requests and console messagesNot tested
- Automate actions in Chrome browserNot tested
How far pickfit got
Linux x86_64
- Installs
- Connects
- 0 of 3 features work
- Works offline
Good for
- Check performance of a website
- Analyze network requests and console messages
- Debug and automate web pages
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
An MCP client connects and lists its tools
- Replayed from scratch
- Works offline
- Checked on 4 Nov 2026
- Version 1.12.0
An MCP client handshake over stdio listed 32 tools.
Differences the test machine hit
- README: Requires Chrome current stable version or newer
In the test: global npm install to ~/.local plus a locally installed Chrome binary via @puppeteer/browsers; bundled Chrome still failed to start: libnspr4.so missing, system libraries need apt/root - README: MCP config uses npx -y chrome-devtools-mcp@latest which fetches on every launch
In the test: run installed binary chrome-devtools-mcp directly so rerun works with network off