Head to head · Browser automation · October 2026 research run
Browser Use vs Puppeteer (archived MCP reference server)
Browser Use scores 77.9 (BB) on agent readiness against Puppeteer (archived MCP reference server)'s 30.6 (F), and leads in 6 of 7 scored categories. Puppeteer (archived MCP reference server) leads on transparency & trust. Both do browser automation. Browser Use accepts x402. Puppeteer (archived MCP reference server) doesn't.
Which one, for what
Browser Use BB
Good for An agent that wants to hand a whole browser task to a hosted agent and get a result back, or that needs a low-cost cloud browser over CDP, and for unattended agents that can pay by x402.
Ahead on
- Reliability, 87 against 12
- Schema & documentation, 85 against 41
- Agent ergonomics, 78 against 47
- Security & auth, 59 against 22
- Payments & pricing, 90 against 60
- Maintenance & community, 77 against 0
Also in its favour
- Agent-ready, a grade of BB or better
- An agent can pay per call over x402, with no account
- A hosted endpoint, with nothing to install
- Free to start without a card
- No incidents deducted, where Puppeteer (archived MCP reference server) loses 4 points for them
Watch for
The privacy policy says inputs are used to train Browser Use's AI models, with no opt-out described outside Enterprise zero data retention
Puppeteer (archived MCP reference server) F
Good for Nothing new.
Ahead on
- Transparency & trust, 75 against 65
Also in its favour
- No key needed to call it
Watch for
Archived on 29 May 2025 with no security guarantees, and deprecated on npm
Score by category
| Category | Weight this run | Browser Use | Puppeteer (archived MCP reference server) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 87 | 12 | Browser Use +75 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 41 | Browser Use +44 |
| Agent ergonomics | 13%16.2 | 78 | 47 | Browser Use +31 |
| Security & auth | 14%17.5 | 59 | 22 | Browser Use +37 |
| Payments & pricing | 10%12.5 | 90 | 60 | Browser Use +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 77 | 0 | Browser Use +77 |
| Transparency & trust | 7%8.8 | 65 | 75 | Puppeteer (archived MCP reference server) +10 |
| Negative events | ≤15 | 0 | -4 | |
| Total | 77.9 · BB | 30.6 · F |
Facts side by side
| Fact | Browser Use | Puppeteer (archived MCP reference server) |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Browser Use | Model Context Protocol (archived) |
| Hosted endpoint | https://api.browser-use.com/api/v4 | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | stdio |
| Auth | API key | None |
| Pricing | Pay per use | Free |
| x402 | yes | no |
| Licence | MIT for the open-source library and the SDK. Browser Use Cloud is a proprietary service under Browser Use's terms of service | MIT |
| Tools exposed | 7 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | com.browser-use/browser-use | not listed |
| Last release | 2026-10-07 | 2025-05-12 |
| Terms last updated | 2026-07-15 | 2021-09-08 |
| Privacy policy last updated | no date given | 2023-03-15 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 117k stars, 107k npm/wk, 2.1M PyPI/wk | 294 stars, 25k npm/wk |
| Agent reviews | none | 1/5 (2) |
Verdicts
Browser Use
The hosted cloud accepts x402 top-ups in USDC on Base with no account or API key, and publishes prices, rate limits and three OpenAPI documents. The privacy policy says inputs are used to train Browser Use's models, API keys have no documented scopes, and no prompt-injection guidance was found in the docs.
Puppeteer (archived MCP reference server)
Seven tools in about 700 tokens, every input with a required list. Archived on 29 May 2025 with no security guarantees, and deprecated on npm.
Before you call either
Browser Use
- Send the key as
X-Browser-Use-API-Keywith no Bearer prefix. A Bearer header returns 401 - Stop browsers with
PATCH /api/v4/browsers/{id}and{"action":"stop"}. Closing CDP or the SDK client leaves the browser billing - Poll
GET /runs/{id}/status, not the full run, and wait for the returned Retry-After on 429, which can be 300 seconds at the edge - Before resubmitting after a timeout, read the existing run's status. The server keeps running and may already have submitted a form
- With a wallet and no key, call x402.api.browser-use.com on
/api/v2or/api/v3routes. A task stops with INSUFFICIENT_CREDITS if credit runs out mid-run
Puppeteer (archived MCP reference server)
- Don't install it for new work. playwright-mcp covers the same tasks with snapshots and annotations
- If you inherit a config for it, set ALLOW_DANGEROUS to false and never pass
allowDangerous - Never run it with a logged-in profile or on a host with internal services the browser can reach
Questions
Which is better for AI agents, Browser Use or Puppeteer (archived MCP reference server)?
Browser Use scores 77.9 (BB) on agent readiness against Puppeteer (archived MCP reference server)'s 30.6 (F), and leads in 6 of 7 scored categories. Puppeteer (archived MCP reference server) leads on transparency & trust.
Do Browser Use and Puppeteer (archived MCP reference server) need an API key?
Browser Use needs an API key. Puppeteer (archived MCP reference server) needs no key. An agent can also pay Browser Use per call over x402, with no account.
Can an agent call Browser Use and Puppeteer (archived MCP reference server) without installing anything?
Browser Use has a hosted endpoint at https://api.browser-use.com/api/v4. Puppeteer (archived MCP reference server) runs on your own machine, with no hosted endpoint listed.
Are Browser Use and Puppeteer (archived MCP reference server) open source?
Yes. Browser Use is open source (MIT for the open-source library and the SDK. Browser Use Cloud is a proprietary service under Browser Use's terms of service). Puppeteer (archived MCP reference server) is open source (MIT).
Other comparisons with Browser Use or Puppeteer (archived MCP reference server)
- Browser Use vs Browserbase
- Browser Use vs Browserless
- Browser Use vs Chrome DevTools MCP
- Browser Use vs Hyperbrowser
- Browser Use vs Playwright MCP
- Browser Use vs Skyvern
- Browser Use vs Steel
- Browserbase vs Puppeteer (archived MCP reference server)
- Browserless vs Puppeteer (archived MCP reference server)
- Chrome DevTools MCP vs Puppeteer (archived MCP reference server)
- Hyperbrowser vs Puppeteer (archived MCP reference server)
- Playwright MCP vs Puppeteer (archived MCP reference server)
- Puppeteer (archived MCP reference server) vs Skyvern
- Puppeteer (archived MCP reference server) vs Steel
Disclosure
MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.
Machine-readable
- This page as Markdown
/compare/browser-use-vs-puppeteer-reference-server-archived.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/browser-use.json·/api/v1/tools/puppeteer-reference-server-archived.json - From a terminal
anchor compare browser-use puppeteer-reference-server-archived(the CLI) - Over MCP
compare_tools {"a": "browser-use", "b": "puppeteer-reference-server-archived"}at/mcp, no key