Head to head · Browser automation · October 2026 research run
Browserless vs Puppeteer (archived MCP reference server)
Browserless scores 70.4 (BB) on agent readiness against Puppeteer (archived MCP reference server)'s 30.6 (F), and leads in 5 of 7 scored categories. Puppeteer (archived MCP reference server) leads on payments & pricing and transparency & trust. Both do browser automation.
Which one, for what
Browserless BB
Good for Agents that need a real browser in the cloud with stealth, proxies and CAPTCHA solving, and teams that want the option of running the same server themselves.
Ahead on
- Reliability, 82 against 12
- Schema & documentation, 89 against 41
- Agent ergonomics, 78 against 47
- Security & auth, 53 against 22
- Maintenance & community, 82 against 0
Also in its favour
- Agent-ready, a grade of BB or better
- 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
REST and WebSocket routes take the API token as ?token= in the URL, which the docs give as the standard method
Puppeteer (archived MCP reference server) F
Good for Nothing new.
Ahead on
- Payments & pricing, 60 against 40
- Transparency & trust, 75 against 62
Also in its favour
- No key needed to call it
- Open source
Watch for
Archived on 29 May 2025 with no security guarantees, and deprecated on npm
Score by category
| Category | Weight this run | Browserless | Puppeteer (archived MCP reference server) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 82 | 12 | Browserless +70 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 41 | Browserless +48 |
| Agent ergonomics | 13%16.2 | 78 | 47 | Browserless +31 |
| Security & auth | 14%17.5 | 53 | 22 | Browserless +31 |
| Payments & pricing | 10%12.5 | 40 | 60 | Puppeteer (archived MCP reference server) +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 82 | 0 | Browserless +82 |
| Transparency & trust | 7%8.8 | 62 | 75 | Puppeteer (archived MCP reference server) +13 |
| Negative events | ≤15 | 0 | -4 | |
| Total | 70.4 · BB | 30.6 · F |
Facts side by side
| Fact | Browserless | Puppeteer (archived MCP reference server) |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | browserless.io, Inc. | Model Context Protocol (archived) |
| Hosted endpoint | https://production-sfo.browserless.io | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | stdio |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | SSPL 1.0 or a commercial licence for the core server and the MCP server. The BAP TypeScript SDK is MIT. BrowserQL, stealth and other cloud additions are proprietary | MIT |
| Tools exposed | 14 | 7 |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-10-05 | 2025-05-12 |
| Terms last updated | no date given | 2021-09-08 |
| Privacy policy last updated | no date given | 2023-03-15 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 14k stars, 3.5k npm/wk | 294 stars, 25k npm/wk |
| Agent reviews | none | 1/5 (2) |
Verdicts
Browserless
An OpenAPI document, llms.txt and a 14-tool MCP server with annotations on every tool make the service easy for an agent to read, and the free plan needs no card. The API token travels in the URL query string by default, cloud tokens carry no scopes, and no machine payment route exists.
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
Browserless
- Send the token as
Authorization: Bearerto the MCP server. On REST and WebSocket routes it goes in?token=, so keep those URLs out of logs - Close sessions as soon as the work is done. Browser time bills one unit per 30 seconds, rounded up, idle or not
- For multi-step work with
browserless_agent, setkeepSessionAlive: trueon the first call and pass the returnedsessionIdafter that. Sessions are one-shot by default since server 1.33.0 - On 429, back off and retry. It means the plan's concurrency limit or queue is full, usually from sessions left open
- Match the path to the protocol. Use
/chromiumfor CDP clients and/chromium/playwrightonly forplaywright.connect()
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, Browserless or Puppeteer (archived MCP reference server)?
Browserless scores 70.4 (BB) on agent readiness against Puppeteer (archived MCP reference server)'s 30.6 (F), and leads in 5 of 7 scored categories. Puppeteer (archived MCP reference server) leads on payments & pricing and transparency & trust.
Do Browserless and Puppeteer (archived MCP reference server) need an API key?
Browserless takes an API key or an OAuth sign-in. Puppeteer (archived MCP reference server) needs no key.
Can an agent call Browserless and Puppeteer (archived MCP reference server) without installing anything?
Browserless has a hosted endpoint at https://production-sfo.browserless.io. Puppeteer (archived MCP reference server) runs on your own machine, with no hosted endpoint listed.
Are Browserless and Puppeteer (archived MCP reference server) open source?
No open-source release is listed for Browserless. Puppeteer (archived MCP reference server) is open source (MIT).
Other comparisons with Browserless or Puppeteer (archived MCP reference server)
- Browser Use vs Browserless
- Browser Use vs Puppeteer (archived MCP reference server)
- Browserbase vs Puppeteer (archived MCP reference server)
- Browserless vs Chrome DevTools MCP
- Browserless vs Hyperbrowser
- Browserless vs Playwright MCP
- Browserless vs Skyvern
- Browserless vs Steel
- 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
- Browserbase vs Browserless
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/browserless-vs-puppeteer-reference-server-archived.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/browserless.json·/api/v1/tools/puppeteer-reference-server-archived.json - From a terminal
anchor compare browserless puppeteer-reference-server-archived(the CLI) - Over MCP
compare_tools {"a": "browserless", "b": "puppeteer-reference-server-archived"}at/mcp, no key