chrome-devtools-mcp
Chrome DevTools for coding agents
Runssource: GitHubhomepageTypeScriptApache-2.0commit b2007ab86639
TypeScript, Apache-2.0 licensed. The project labels itself: browser, chrome, chrome devtools, debugging, devtools, mcp, mcp server and puppeteer.
chrome-devtools-mcp runs. An Argusic agent installed it in 44 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The project builds, all tests pass (including e2e), and both CLI and MCP server start successfully using the puppeteer-installed Chrome browser.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Chrome not found at /opt/google/chrome/chrome (system path), failing e2e tests.5 minutes
- Node.js v18 on host, project requires >=22.12.0. Downloaded and used Node.js v22.13.0 from binary tarball.2 minutes
- prepare.ts is a TypeScript file that cannot be run directly by Node.js without a TS runner.2 minutes
- post-build.ts has the same issue as prepare.ts.2 minutes
- Chrome not installed. Puppeteer browsers install failed: missing unzip and empty cache directory.2 minutes
- Chrome sandbox prevents launch in container without --no-sandbox.1 minute
- Install time
- 44 minutes
- Cold machine to finish
- 51 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- Model tokens used
- 373,233
- Exact commit tested
- b2007ab86639
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **Sandbox**: Set `PUPPETEER_DANGEROUS_NO_SANDBOX=true` - **Chrome discovery**: Patched `browser.ts` to respect `PUPPETEER_EXECUTABLE_PATH` env var, solvin… All tests pass (exit code 0), both CLI and MCP server start successfully. tokens used 373,233 The project is fully functional now. The key fixes made: - **Node.js**: Installed v22.13.0 to satisfy project requirements - **TS scripts**: Converted `prepare.ts` and `post-build.ts` to `.mjs` since no native TS runner is… - **Chrome installation**: Installed via puppeteer after resolving `unzip` dependency issue with `y… - **Sandbox**: Set `PUPPETEER_DANGEROUS_NO_SANDBOX=true` - **Chrome discovery**: Patched `browser.ts` to respect `PUPPETEER_EXECUTABLE_PATH` env var, solvin… All tests pass (exit code 0), both CLI and MCP server start successfully.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 44 minutes.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs | 100.00 | 0.32 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.21 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.21 |
Topics (from GitHub)
browserchromechrome-devtoolsdebuggingdevtoolsmcpmcp-serverpuppeteer
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/chrome-devtools-mcp)Questions
- Does chrome-devtools-mcp run?
- Yes. chrome-devtools-mcp runs. Argusic installed and launched it on a clean machine in 44 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test chrome-devtools-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b2007ab86639. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test chrome-devtools-mcp?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does chrome-devtools-mcp take to install?
- 44 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does chrome-devtools-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing chrome-devtools-mcp?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for chrome-devtools-mcp?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.