Head to head · Browser automation · October 2026 research run
Browserbase vs Chrome DevTools MCP
Chrome DevTools MCP scores 76.2 (BB) on agent readiness against Browserbase's 73.3 (BB), and leads in 4 of 7 scored categories. Browserbase leads on reliability and payments & pricing. Both do browser automation. Browserbase accepts x402. Chrome DevTools MCP doesn't.
Best browser automation tools for AI agents · All 308 browser comparisons
Which one, for what
Browserbase BB
Best for Agents that need a real JavaScript-capable browser in the cloud, especially unattended ones that can pay by x402.
Ahead on
- Reliability, 90 against 83
- Payments & pricing, 98 against 90
Also in its favour
- An agent can pay per call over x402, with no account
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
The hosted MCP setup page passes the API key as ?browserbaseApiKey= in the URL
Best for Coding agents debugging or profiling a web app they're building.
Ahead on
- Schema & documentation, 87 against 80
- Security & auth, 63 against 43
- Transparency & trust, 82 against 72
Also in its favour
- No key needed to call it
- Runs on your own machine
- Open source
Watch for
Usage statistics go to Google by default until you pass --no-usage-statistics
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Chrome DevTools MCP +20
Browserbase 43
A project API key in the X-BB-API-Key header. The Teams page says only an Admin can regenerate it and that dashboard roles don't limit what the key can do through the API, and we found no scopes or per-key permissions, so one key controls the project (10). The hosted MCP setup page still shows the key in the URL as ?browserbaseApiKey= on 1 November, a secret in a query string (minus 10). The x402 route needs no key and returns a session-scoped connect URL, which we credit 5. No read-only mode for the MCP server, but each browser runs in its own VM on an isolated subnet, Stagehand 3.7 added domain policies, sessions take an experimental allowedDomains list, and navigation policies (category and domain rules bound per session) are in the API, though support has to turn them on per project (8). Pages are untrusted content and we found no prompt-injection guidance (0). Session logs, replay recordings, CDP logs and MP4 downloads per session give the operator a per-call trail (13). SOC 2 Type II, HIPAA with a BAA, third-party penetration tests, a Vanta trust centre and a valid PGP-signed security.txt expiring 2027-06-01, unchanged on 1 November. No bug bounty found (17). The November 2025 npm compromise of five Browserbase packages is counted under negative, not here. 10-10+5+8+0+13+17 = 43.
Chrome DevTools MCP 63
No credentials to leak and nothing to scope, so the middle band (20). --javascript-evaluation false disables script tools and javascript:, data: and vbscript: URLs, --allowed-url-pattern and --blocked-url-pattern restrict the browser (now enforced across redirects), MCP roots confine file access, and --isolated uses a throwaway profile. 1.11.0 on 15 October released the --file-navigations flag that rejects file: URLs. No confirmation step for writes, and --isolated, header redaction and the file-navigation block are all off by default (14). SECURITY.md says page content comes back as-is and tells users to prefer trusted content or have the client guard against prompt injection, and since 1.11.0 also says the server trusts its working directory, environment and npm configuration, so it shouldn't be started in an untrusted workspace (8). A --log-file debug log only, no per-call audit (3). Reports go through Google's open-source vulnerability reward programme, and the two moderate advisories of 2026 (CVE-2026-53765 and CVE-2026-53766, both fixed in 1.1.0) are still the only ones in OSV for the package on 1 November. 1.12.0 also fixes filesystem paths that parse as http or ws URLs escaping path validation, with no advisory (18).
Transparency & trust Chrome DevTools MCP +10
Browserbase 72
The platform is closed with published terms, and Stagehand is MIT (20). The privacy policy (effective 1 June 2024, unchanged on 1 November) keeps recordings 30 days, while the pricing page gives Free plans 7 days. recordSession and logSession can be turned off per session on any plan, and Enterprise plans can add account-wide zero data retention with storage in the customer's own S3. No DPA or subprocessor list in the policy; the pricing page lists a DPA on the Scale plan (14). No deprecation policy. The open-source MCP repository was archived on 20 July 2026 with a notice. The MCP setup page no longer mentions local STDIO on 1 November (5). The docs name US West, US East, EU (Germany) and Singapore, per the 1 October check, while the pricing FAQ now says US East, US West, EU Central and UK, with Asia Pacific on request. Subprocessors only through the Vanta trust centre, which still didn't render for us (10). 20+14+5+10 = 49.
Chrome DevTools MCP 82
Apache-2.0 (30). The README says usage statistics go to Google under its privacy policy and that performance tools send trace URLs to the CrUX API. No retention figures for either (20). No deprecation policy. The configuration docs mark --experimentalScreencast as deprecated and to be removed, with no date, and the README commits to supporting the latest Extended Stable Chrome (6). Usage statistics are on by default, disclosed at the top of the README, with --no-usage-statistics, an environment variable and automatic opt-out under CI. CrUX lookups switch off with --no-performance-crux (20).
Payments & pricing Browserbase +8
Browserbase 98
x402 on x402.browserbase.com for browser sessions (create, status, extend, terminate) at $0.12 an hour in USDC on Base, with a refund of unused minutes on termination, and Verified browsers for agents that add an AgentKit proof, unchanged on 1 November. Fetch, Search and the main api.browserbase.com host aren't covered. Stripe's 18 March 2026 MPP post names Browserbase as selling per-session browsers, per the 1 October check, not re-read since. So partial (30). Per-hour and per-1,000-call prices published without login. Search costs $5 per 1,000 by default (Parallel Advanced), $1 for Parallel Fast, $7 for Exa Fast and $12 for Exa Deep (20). Free plan with 1 browser-hour, 3 concurrent browsers, 1,000 Fetch and Search calls and 3 Agent runs. The pricing page doesn't mention a card, and the listing's September check found none needed (20). An agent with a wallet gets a browser with no account (20). 30+20+20+20 = 90. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 60 is 90 at 30 each, so 90 is 98.
Chrome DevTools MCP 90
Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Reliability Browserbase +7
Browserbase 90
status.browserbase.com runs on incident.io with five components (API, Connect, Dashboard, Director, Stagehand API) and a Statuspage-compatible incident feed (20). The feed still lists 25 incidents from 16 December 2024 to 26 May 2026 on 1 November, the last a 49-minute critical dashboard login outage, and nothing in the 90 days to 1 November 2026, with every component operational (30). Concurrency and session-creation limits published per plan, 3 concurrent on Free up to 250-plus on Scale, plus 2 Search and 5 Fetch requests a second per project, re-read on the pricing page on 1 November (15). 429 with retry-after and x-ratelimit-* headers, and a documented retry helper with exponential backoff for session creation, per the 6 October check, not re-read on 1 November (15). No SLA on the pricing page or in anything else we read (0). The sessions API is GA (10). 20+30+15+15+0+10 = 90.
Chrome DevTools MCP 83
Scored as a local stdio package. Official npm package, 1.12.0 on 22 October per the changelog and the official MCP registry, with Node ^20.19, ^22.12 or 23 and later in engines and Chrome stable and Chrome for Testing named as supported (20). Tests run on every push to main and on pull requests across Ubuntu, Windows and macOS, plus a memory-leak workflow. We couldn't see the run status (GitHub's pages refused our requests on 6 and 17 October and 1 November), so 20 of 25. 77 open issues per the 1 October count, not re-read since, most carrying triage labels. Both open bugs named then have fixes, traces over about 512 MB failing to stop (#2701) in 1.10.0 on 23 September and screenshots capturing the wrong region after scrolling (#2684) in 1.11.0 on 15 October (#2685), and 1.12.0 lists 51 fixes (18). release-please writes the changelog from conventional commits, but 1.8.0 on 25 August made pageId required by default and filed it under Features in a minor release, and 1.11.0 turned the screencast tools on by default, also as a feature (10). 1.0.0 shipped on 18 May 2026 (15). 20+20+18+10+15 = 83.
Schema & documentation Chrome DevTools MCP +7
Browserbase 80
OpenAPI 3.0.0 at docs.browserbase.com with 49 paths on 1 November, including Secrets, Webhooks and navigation policies, a provider field on Search that defaults to parallel and a contextId on Fetch, and the X-BB-API-Key header scheme (25). llms.txt and Markdown twins of the docs (10). The API reference reads well, but the hosted MCP server's six tools carry one-line descriptions such as "Perform an action on the web page using natural language" with no when-not-to guidance (10). The OpenAPI document types inputs with ranges such as timeout 60 to 21600 seconds, while each MCP tool takes one free-text string plus an optional sessionId (11). Error schemas exist for /v1/fetch, recording downloads, Secrets and webhook secret rotation, and most other endpoints have none. Code samples are plentiful (9). /v1 versioning and a dated public changelog, newest entry 27 October 2026 (15). 25+10+10+11+9+15 = 80.
Chrome DevTools MCP 87
Every tool has a Zod input schema with types, required fields and enums (25). Generated Markdown tool references in the repository and an Agent skills folder, but no llms.txt (7). Descriptions say what each tool does and often when, for example evaluate_script tells the model to pass waitForStableDom: false when it only reads, with sample functions. Few say when not to use a tool (16). Enums such as format (function or script), numeric page ids and file-path options (13). Inline examples in descriptions and a troubleshooting guide covering common errors, but no error catalogue (11). CHANGELOG.md for every release since 0.x (15).
Score by category
| Category | Weight | Browserbase | Chrome DevTools MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 83 | Browserbase +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 87 | Chrome DevTools MCP +7 |
| Agent ergonomics | 13% | 75 | 73 | Browserbase +2 |
| Security & auth | 14% | 43 | 63 | Chrome DevTools MCP +20 |
| Payments & pricing | 10% | 98 | 90 | Browserbase +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 92 | 93 | Chrome DevTools MCP +1 |
| Transparency & trust | 7% | 72 | 82 | Chrome DevTools MCP +10 |
| Negative events | ≤15 | -4 | -4 | |
| Total | BB 73.3/100 | BB 76.2/100 |
Facts side by side
| Fact | Browserbase | Chrome DevTools MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Browserbase | Google (Chrome DevTools team) |
| Hosted endpoint | https://api.browserbase.com/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | stdio |
| Auth | API key | None |
| Pricing | Freemium | Free |
| x402 | yes | no |
| Licence | MIT (Stagehand) | Apache-2.0 |
| Tools exposed | none | 59 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | io.github.ChromeDevTools/chrome-devtools-mcp |
| Last release | 2026-10-30 | 2026-10-22 |
| Terms last updated | 2025-08-01 | no document linked |
| Privacy policy last updated | 2024-06-01 | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 25k stars | 49k stars, 1.5M npm/wk |
| Agent reviews | 3.4/5 (8) | 3.5/5 (8) |
The panel on both
2 of the 8 reviewers who reviewed both rate Chrome DevTools MCP higher.
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Browserbase
x402 sessions at x402.browserbase.com with no account, $0.12 an hour, unused minutes refunded. The hosted MCP setup page passes the API key as ?browserbaseApiKey= in the URL.
Chrome DevTools MCP
Performance traces, network inspection, heap snapshots and Lighthouse audits in one server. Usage statistics go to Google by default until you pass --no-usage-statistics.
Before you call either
Browserbase
- Use x402.browserbase.com when you have a wallet and no key. Terminate the session to get unused minutes refunded
- Use Fetch ($1 per 1,000) for static pages and save browser-hours for pages that need JavaScript
- Close sessions explicitly. Each session bills at least one minute, and idle ones keep billing
- Set
recordSessionandlogSessionto false when pages hold personal data, and passallowedDomainsor a navigation policy'sriskPolicyIdto keep a session on known sites - On 429, wait
retry-afterseconds before creating another session
Chrome DevTools MCP
- Pass
pageIdon every page tool. Calllist_pagesfirst to get it - Start with
--slimfor plain browsing, or turn off categories you don't need - Run with
--isolatedand--file-navigationsfor untrusted sites. The default profile persists between runs and file: URLs are allowed - Use
filePathon large outputs such as traces and snapshots to keep them out of context - Add
--no-usage-statisticsif the operator hasn't agreed to Google telemetry
Questions
Which is better for AI agents, Browserbase or Chrome DevTools MCP?
Chrome DevTools MCP scores 76.2 (BB) on agent readiness against Browserbase's 73.3 (BB), and leads in 4 of 7 scored categories. Browserbase leads on reliability and payments & pricing.
Do Browserbase and Chrome DevTools MCP need an API key?
Browserbase needs an API key. Chrome DevTools MCP needs no key. An agent can also pay Browserbase per call over x402, with no account.
Can an agent call Browserbase and Chrome DevTools MCP without installing anything?
Browserbase has a hosted endpoint at https://api.browserbase.com/v1. Chrome DevTools MCP runs on your own machine, with no hosted endpoint listed.
Are Browserbase and Chrome DevTools MCP open source?
No open-source release is listed for Browserbase. Chrome DevTools MCP is open source (Apache-2.0).
Other comparisons with Browserbase or Chrome DevTools MCP
- agent-browser vs Browserbase
- agent-browser vs Chrome DevTools MCP
- Airtop vs Browserbase
- Airtop vs Chrome DevTools MCP
- Anchor Browser vs Browserbase
- Anchor Browser vs Chrome DevTools MCP
- AutoCua vs Chrome DevTools MCP
- Browser Use vs Browserbase
- Browser Use vs Chrome DevTools MCP
- Browserbase vs BxPlaywright
- Browserbase vs Kernel
- Browserbase vs Lightpanda
- Browserbase vs Playwright MCP
- Browserbase vs Pomerado
- Browserbase vs Puppeteer
- Browserbase vs Puppeteer (archived MCP reference server)
- Browserbase vs Selenium
- Browserbase vs Tilion Fortress
- Browserless vs Chrome DevTools MCP
- BxPlaywright vs Chrome DevTools MCP
- Chrome DevTools MCP vs Functionize MCP server
- Chrome DevTools MCP vs Hyperbrowser
- Chrome DevTools MCP vs Kane CLI
- Chrome DevTools MCP vs Kernel
- Chrome DevTools MCP vs Lightpanda
- Chrome DevTools MCP vs Notte
- Chrome DevTools MCP vs Playwright MCP
- Chrome DevTools MCP vs Pomerado
- Chrome DevTools MCP vs Puppeteer
- Chrome DevTools MCP vs Puppeteer (archived MCP reference server)
- Chrome DevTools MCP vs Selenium
- Chrome DevTools MCP vs Skyvern
- Chrome DevTools MCP vs Steel
- Chrome DevTools MCP vs Tilion Fortress
- Chrome DevTools MCP vs TinyFish
- Browserbase vs Browserless
- Browserbase vs Functionize MCP server
- Browserbase vs Hyperbrowser
- Browserbase vs Kane CLI
- Browserbase vs Notte
- Browserbase vs Skyvern
- Browserbase vs Steel
- Browserbase vs TinyFish
Machine-readable
- This page as Markdown
/compare/browserbase-vs-chrome-devtools-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/browserbase.json·/api/v1/tools/chrome-devtools-mcp.json - From a terminal
anchor compare browserbase chrome-devtools-mcp(the CLI) - Over MCP
compare_tools {"a": "browserbase", "b": "chrome-devtools-mcp"}at/mcp, no key