mcp-chrome
Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search.
Runs with mockssource: GitHubTypeScriptMITcommit f48e71751e00
TypeScript, MIT licensed.
mcp-chrome runs, with stand-ins for the services it depends on. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The monorepo builds successfully (packages/shared, app/chrome-extension, app/native-server), all 642 tests pass, the CLI responds to help/doctor commands, and the MCP stdio server starts without errors.
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 92 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.
- System Node.js v18.19.1 is below the project's requirement of Node >= 20, preventing pnpm install and builds2 minutes
- pnpm 12 blocks build scripts (better-sqlite3, esbuild, sharp, etc.) by default, failing pnpm install2 minutes
- Original jest.config.js with ts-jest fails to resolve .js extension imports (NodeNext module resolution) and coverage thresholds block tests from running2 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- Model tokens used
- 60,895
- Exact commit tested
- f48e71751e00
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
specifier: ^8.32.0 - version: 8.49.0(@typescript-eslint/[email protected])([email protected])([email protected]) + version: 8.69.0(@typescript-eslint/[email protected]([email protected]([email protected])(supports-color@… '@typescript-eslint/parser': specifier: ^8.32.0 - version: 8.49.0([email protected])([email protected]) The lockfile was upgraded from v6 to v9 (pnpm v12 format) which explains the large diff. This is ex… Now let me compile the results. Here's my summary: tokens used 60,895 The lockfile was upgraded from v6 to v9 (pnpm v12 format) which explains the large diff. This is ex… Now let me compile the results. Here's my summary:
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
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 8 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
Of the 6 TypeScript projects Argusic has installed and timed, mcp-chrome was the 4th fastest to reach a running state, and 5 of 6 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.07 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.07 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.07 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcp-chrome)Questions
- Does mcp-chrome run?
- mcp-chrome runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test mcp-chrome?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f48e71751e00. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mcp-chrome?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcp-chrome take to install?
- 8 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 mcp-chrome need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcp-chrome?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mcp-chrome compare with the alternatives?
- Of the 6 TypeScript projects Argusic has installed and timed, mcp-chrome was the 4th fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for mcp-chrome?
- 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.