browser-tools-mcp
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
Runssource: GitHubhomepageTypeScriptMITcommit 99acee8d02f1
TypeScript, MIT licensed. The project labels itself: ai, anthropic, cursor, mcp and mcp server.
browser-tools-mcp runs. An Argusic agent installed it in 0.7 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The BrowserTools MCP workspace installs, builds, and passes all 356 unit and integration tests with Node 22.14.0. The MCP server binary prints version 2.0.2, help with 16 tools, and runs --doctor setup checks.
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.
- Integration test 'still produces a usable client when the connector cannot start' failed because port 1 was not privileged in this container (the test assumed EACCES, but the runner user can bind low ports).0.2 minutes
- Install time
- under a minute
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 356 passed (20 test files). Node dist/index.js --version printed 2.0.2. node dist/index.js --help printed usage with 16 tools. node dist/index.js --doctor ran setup check reporting 2 expected warnings (no Chrome extension connected, no Chromium for audits).
- Model tokens used
- 66,699
- Exact commit tested
- 99acee8d02f1
- 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.
- 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.
**One bug found and fixed:** The integration test "still produces a usable client when the connecto… **Verification:** `node dist/index.js --version` prints `2.0.2`, `node dist/index.js --help` prints… **Third-party keys:** The project uses Chrome extension + connector model — no external API keys ne… tokens used 66,699 Everything works. Let me compute the final aggregated result. Here's the summary of my work: **Install:** `npm install` succeeded (303 packages). TypeScript build (`npm run build`) succeeded. **Test suite (the key verification):** `npm test` = all 356 tests pass across 20 test files (11 uni… **One bug found and fixed:** The integration test "still produces a usable client when the connecto… **Verification:** `node dist/index.js --version` prints `2.0.2`, `node dist/index.js --help` prints… **Third-party keys:** The project uses Chrome extension + connector model — no external API keys ne…
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 0.7 minutes, faster than the median of the 56 comparable projects Argusic has measured.
- Recovered from all 1 error 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 MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 57 ai projects Argusic has installed and timed, browser-tools-mcp was the 7th fastest to reach a running state, and 44 of 57 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.7 minutes after the clone.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/browser-tools-mcp)Questions
- Does browser-tools-mcp run?
- Yes. browser-tools-mcp runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test browser-tools-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 99acee8d02f1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test browser-tools-mcp?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does browser-tools-mcp take to install?
- 0.7 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 browser-tools-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing browser-tools-mcp?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does browser-tools-mcp compare with the alternatives?
- Of the 57 ai projects Argusic has installed and timed, browser-tools-mcp was the 7th fastest to reach a running state, and 44 of 57 reached one at all.
- Where is the evidence for browser-tools-mcp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.