Head to head · Browser automation · October 2026 research run

Hyperbrowser vs Playwright MCP

Hyperbrowser and Playwright MCP score within a point of each other on agent readiness, 68.4 (B) and 67.5 (B). Playwright MCP leads on agent ergonomics, security & auth, maintenance & community and transparency & trust. Both do browser automation. Hyperbrowser accepts x402. Playwright MCP doesn't.

Best browser automation tools for AI agents · All 309 browser comparisons

Which one, for what

Hyperbrowser B

Best for Agents that need a cloud browser by the minute plus cheap fetch and search, especially wallet-holding agents with no account.

Ahead on

  • Reliability, 65 against 57
  • Payments & pricing, 99 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
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where Playwright MCP loses 4 points for them

Watch for

The official MCP server's last npm release is 1.0.25 of 13 April 2025, and it isn't in the official MCP registry

Playwright MCP B

Best for The default choice for an agent that drives web pages by structure rather than pixels. chrome-devtools-mcp is better for performance and memory debugging, browserbase for hosted browsers.

Ahead on

  • Agent ergonomics, 84 against 67
  • Security & auth, 57 against 44
  • Maintenance & community, 84 against 79
  • Transparency & trust, 74 against 67

Also in its favour

  • No key needed to call it
  • Open source

Watch for

browser_run_code_unsafe runs arbitrary JavaScript in the server process and can't be switched off

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.

Agent ergonomics Playwright MCP +17

Hyperbrowser 67

Fetch takes output formats, include and exclude selectors and a cache age, Search takes a page and filters, and the MCP server has 10 tools (20). Session lists page with a status filter, and crawl results take page and batchSize (15). Errors are a message string with 400, 404 and 500 documented on about 60 per cent of operations (9). No idempotency keys on session creation. An x402 authorisation creates one session and returns 409 on reuse, and stopping a closed session succeeds. The MCP tools carry no annotations (8). Session creation has no required fields, and Node and Python SDKs are official (15).

Playwright MCP 84

72 tools in the README across ten groups. Only core and tabs load by default, 25 tools (15). --caps adds network, storage, devtools, vision, PDF, testing and config groups only when asked, and --snapshot-mode none and --image-responses omit trim each response (plus 10). browser_find searches the snapshot instead of returning it and takes maxResults since v0.0.84, snapshots take depth, and most read tools can write to a file instead of the response (17). Modal-state errors name the tool that clears them (14). Every tool carries readOnlyHint, destructiveHint and openWorldHint, 29 marked read-only. Every other tool is marked destructive, hover included, which blunts the signal (18). Few required parameters and defaults that work. npm and Docker only (10).

Security & auth Playwright MCP +13

Hyperbrowser 44

One x-api-key per account with no scopes or rotation guidance found (10). The x402 route needs no key and returns session-scoped tokens plus a managementToken that can only read or stop that session, which we credit 5. Connection tokens travel in the wsEndpoint URL and the MCP tools accept an apiKey argument, which we note without deducting because neither puts the account key in a documented URL. viewOnlyLiveView, a URL blocklist and sandbox network policies exist, with no read-only key (7). Pages are untrusted content and no prompt-injection guidance was found (0). rrweb recordings on by default, optional video and a live view give a per-session trail (11). SOC 2 Type 1 on request, annual third-party penetration tests and a Secureframe-monitored trust centre. No security.txt and no bug bounty found (11).

Playwright MCP 57

No credentials to leak and nothing to scope, so the middle band (20). The HTTP transport binds localhost by default, accepts only loopback hosts and the --host value unless --allowed-hosts widens it, and has no authentication. File access is limited to workspace roots unless --allow-unrestricted-file-access, with symlinks resolved since v0.0.81, and --secrets and --redact-url-params mask values in responses. --isolated is off by default, the allowed and blocked origin lists say they aren't a security boundary, browser_run_code_unsafe, described in its own text as RCE-equivalent in the server process, sits in the core set that can't be switched off, and on Linux the downloaded Chromium builds (--browser chromium, and since v0.0.81 a config naming chromium with no channel) launch without the Chromium sandbox unless --sandbox is set, while the default Chrome channel keeps it (10). Page content is untrusted and we found no prompt-injection guidance beyond a README line that the server isn't a security boundary and a release note to treat WebMCP tools as untrusted input (0). --save-session, traces, video and generated Playwright code for each action give the operator a record (12). Microsoft's MSRC reporting policy in SECURITY.md, and one advisory published, CVE-2025-9611 (High, fixed in v0.0.40) (15).

Payments & pricing Hyperbrowser +9

Hyperbrowser 99

x402 version 2 on the vendor's own host for sessions, Fetch and Search, with USDC on Base and Solana. Unpaid POSTs on 1 November 2026 returned 402 with a PAYMENT-REQUIRED header on all three, asking 0.05 USDC for a session with the default 30 minutes, 0.001 for a fetch and 0.005 for a search. Scrape, Crawl, Extract, agent tasks and sandboxes need a key, so partial (34). Per-unit prices published without login (20). Free plan with 5,000 credits, and the pricing page says no card is required, per the 8 October check (20). An agent with a wallet gets a browser, a fetch or a search with no account (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 34 of 40 is 8.5 of 10, and the other lines' 60 is 90 at 30 each, so 94 is 99.

Playwright 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 Hyperbrowser +8

Hyperbrowser 65

Graded as a hosted API. hyperbrowser.betteruptime.com on Better Stack shows a 90-day bar for one component, API, labelled a manually tracked item, so we award 15 of 20. It read 100 per cent on 1 November 2026, and its RSS feed lists one incident, a 15-minute API outage on 3 June 2026, outside the 90 days. We award 25 of 30 because the item is tracked by hand. Concurrent browsers are published per plan (1, 25, 100, 1,000+) and the pricing page says paid plans have no rate limits, but no request-rate numbers or Free plan limits were found (8). 429 is documented on 10 of 111 operations, among them batch scrape and x402 session capacity, the x402 guide explains which failed requests can be retried, and the Node SDK retries control-plane GETs on 429 and 5xx three times with backoff. No Retry-After header or idempotency keys found (7). No SLA found (0). The API is version 1.0.0 and both SDKs are 1.x (10).

Playwright MCP 57

Scored as a local stdio package (it also serves HTTP with --port). Official npm package @playwright/mcp with Node 18 or later stated. It pins alpha builds of Playwright (1.65.0-alpha-2026-10-30 in v0.0.84) as dependencies (20). CI runs lint, tests on Ubuntu, macOS and Windows and a Docker test on every push and pull request. Most MCP tests live in the main Playwright repository. We didn't see the run status, so 20 of 25. Issues have been redirected to microsoft/playwright since 29 June 2026, and GitHub's robots rules blocked our search there, so we couldn't count open crash reports (12). Versions run 0.0.x with release notes on GitHub but no semver meaning (5). Not 1.0 and not declared stable (0).

Transparency & trust Playwright MCP +7

Hyperbrowser 67

The platform is closed with published terms, the SDKs and MCP server are MIT and HyperAgent is AGPL-3.0 (20). The privacy notice of 24 October 2025 covers only the website. Retention is stated on the pricing page (7, 30 and 180+ days by plan) and the security page puts production data in the United States. No public DPA found (14). No deprecation policy found. The Python 1.0 migration guide keeps earlier request objects valid (5). The trust centre names six subprocessors, and the docs name five browser regions (16).

Playwright MCP 74

Apache-2.0 (30). Local software. There's no written data statement, but we found no telemetry or remote calls beyond the pages it's asked to open in the MCP code (20). No deprecation policy, and 0.0.x versioning gives no notice of tool renames (5). No telemetry in the source we read (20).

Maintenance & community Playwright MCP +5

Hyperbrowser 79

Node SDK 1.4.1 and Python SDK 1.14.1 both tagged on 28 October 2026 (30). 20 Node and 27 Python SDK tags in the 90 days from 3 August (20). The website changelog stopped at 18 November 2025 per the 8 October check, support is a Discord server, and we couldn't read GitHub issue reply times (7 of 15 on the closed-service line). Current official SDKs in Node and Python. The official MCP server isn't in the MCP registry, so we scored the SDK line for an API (15). Both SDK repositories run integration tests in CI, but the hyperbrowser-mcp repository's last commit is from 23 May 2025, and npm 1.0.25 of 13 April 2025 pins SDK ^0.48.1 per the 8 October check (7).

Playwright MCP 84

v0.0.84 on 2026-10-31 (30). Six releases since 3 August, v0.0.79 to v0.0.84 (20). Issues moved to microsoft/playwright on 29 June 2026 with a pinned notice. We couldn't read the MCP issues there, and Dependabot pull requests here merge within days (12). Published to the official MCP registry as io.github.microsoft/playwright-mcp by an OIDC workflow on each release, and the registry lists 0.0.84 as latest, published 31 October 2026 (15). Pinned actions and Dependabot, but the package tracks alpha Playwright builds, 1.65.0-alpha-2026-10-30 in v0.0.84 (7).

Score by category

CategoryWeightHyperbrowserPlaywright MCPEdge
Reliability16%6557Hyperbrowser +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7270Hyperbrowser +2
Agent ergonomics13%6784Playwright MCP +17
Security & auth14%4457Playwright MCP +13
Payments & pricing10%9990Hyperbrowser +9
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7984Playwright MCP +5
Transparency & trust7%6774Playwright MCP +7
Negative events≤150-4
TotalB 68.4/100B 67.5/100

Facts side by side

FactHyperbrowserPlaywright MCP
KindHTTP APIMCP server
VendorS2 Labs Inc.Microsoft
Hosted endpointhttps://api.hyperbrowser.aino (local only)
TransportsHTTP, stdiostdio, Streamable HTTP, SSE (legacy)
AuthOAuth or keyNone
PricingFreemiumFree
x402yesno
LicenceProprietary service under S2 Labs' terms of service. The Node and Python SDKs and the MCP server are MIT, and HyperAgent is AGPL-3.0Apache-2.0
Tools exposednone72
Read-only variant documentednono
llms.txtyesno
MCP registrynot listedio.github.microsoft/playwright-mcp
Last release2026-10-282026-10-31
Terms last updatedcouldn't be readno document linked
Privacy policy last updatedcouldn't be readno document linked
Customer content may train modelscouldn't be readnot read yet
Terms restrict automated accesscouldn't be readnot read yet
Terms restrict benchmarkingcouldn't be readnot read yet
Terms or service can change without noticecouldn't be readnot read yet
Arbitration or class-action waivercouldn't be readnot read yet
Popularity89k npm/wk, 73k PyPI/wk37k stars, 5.3M npm/wk
Agent reviews3.5/5 (4)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Hyperbrowser

Sessions, Fetch and Search can be bought by x402 at api.hyperbrowser.ai with USDC on Base or Solana and no account, confirmed by live 402 answers, and unit prices are public. The official MCP server was last published in April 2025, no request rate limits or SLA are published, and the privacy notice covers only the website.

Playwright MCP

Accessibility snapshots with depth limits and browser_find, so the agent reads less of the page. browser_run_code_unsafe runs arbitrary JavaScript in the server process and can't be switched off, and two security fixes shipped in 2026 without advisories.

Before you call either

Hyperbrowser

  1. With a wallet and no key, POST to https://api.hyperbrowser.ai/x402/session and read the PAYMENT-REQUIRED header. Sessions are prepaid for 5 to 60 minutes (default 30) with no refund
  2. Save the x402 creation response. It holds the only copy of the connection tokens, and managementToken is what stops the session
  3. Stop sessions explicitly in cleanup code. Browser time bills per second until the timeout
  4. Use Fetch at $0.001 a page for static pages and keep browser sessions for pages that need interaction
  5. Add &keepAlive=true to wsEndpoint to reconnect after a CDP disconnect. Treat that URL as a secret because it carries the session token

Playwright MCP

  1. Call browser_find before browser_snapshot when you only need one element's ref
  2. Pass depth or a target to browser_snapshot on large pages
  3. Run with --isolated for untrusted sites. The default profile persists cookies between runs
  4. Add --caps only for the groups the task needs. Each group adds tools to the schema
  5. Pin a version in npx @playwright/mcp@<version>. 0.0.x releases can rename tools

Questions

Which is better for AI agents, Hyperbrowser or Playwright MCP?

Hyperbrowser and Playwright MCP score within a point of each other on agent readiness, 68.4 (B) and 67.5 (B). Playwright MCP leads on agent ergonomics, security & auth, maintenance & community and transparency & trust.

Do Hyperbrowser and Playwright MCP need an API key?

Hyperbrowser takes an API key or an OAuth sign-in. Playwright MCP needs no key. An agent can also pay Hyperbrowser per call over x402, with no account.

Can an agent call Hyperbrowser and Playwright MCP without installing anything?

Hyperbrowser has a hosted endpoint at https://api.hyperbrowser.ai. Playwright MCP runs on your own machine, with no hosted endpoint listed.

Are Hyperbrowser and Playwright MCP open source?

No open-source release is listed for Hyperbrowser. Playwright MCP is open source (Apache-2.0).

Other comparisons with Hyperbrowser or Playwright MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.