Get an audit

Head to head · Browser automation · October 2026 research run

agent-browser vs Playwright MCP

Playwright MCP scores 67.6 (B) on agent readiness against agent-browser's 66.6 (B), and leads in 4 of 7 scored categories. agent-browser leads on schema & documentation and security & auth. Both do browser automation.

agent-browserVercel Labs · MCP server B66.6/100#263 of 841 Playwright MCPMicrosoft · MCP server B67.6/100#228 of 841

Which one, for what

agent-browser B

Good for Coding agents with a shell that want short commands and compact snapshots.

Ahead on

  • Schema & documentation, 84 against 70
  • Security & auth, 67 against 57

Watch for

The ten most recent CI runs on main, 1 to 8 October 2026, all concluded in failure. In the newest, Windows Rust tests and native end-to-end tests failed

Playwright MCP B

Good 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

  • Reliability, 57 against 48
  • Agent ergonomics, 84 against 78
  • Maintenance & community, 84 against 70
  • Transparency & trust, 72 against 61

Watch for

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

Score by category

CategoryWeight this runagent-browserPlaywright MCPEdge
Reliability16%204857Playwright MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28470agent-browser +14
Agent ergonomics13%16.27884Playwright MCP +6
Security & auth14%17.56757agent-browser +10
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87084Playwright MCP +14
Transparency & trust7%8.86172Playwright MCP +11
Negative events≤1500
Total66.6 · B67.6 · B

Facts side by side

Factagent-browserPlaywright MCP
KindMCP serverMCP server
VendorVercel LabsMicrosoft
Hosted endpointno (local only)no (local only)
Transportsstdiostdio, Streamable HTTP, SSE (legacy)
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Tools exposed15872
Read-only variant documentednono
llms.txtyesno
MCP registrynot listedio.github.microsoft/playwright-mcp
Last release2026-10-012026-09-28
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity44k stars, 2.1M npm/wk37k stars, 5.3M npm/wk
Agent reviewsnone3/5 (2)

Verdicts

agent-browser

Snapshots with element refs, a 29-tool default MCP profile and opt-in domain allowlists, action policies and content boundary markers suit agent use. The project is at 0.38.2 with no stable release, the ten most recent CI runs on main failed between 1 and 8 October 2026, and every security control is off by default.

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.

Before you call either

agent-browser

  1. Run agent-browser install once after npm install -g agent-browser. It downloads Chrome for Testing
  2. Take a fresh snapshot -i after any navigation. Refs survive same-document changes only
  3. Pass --json for machine-readable results and --max-output to cap page text
  4. Set --allowed-domains, --action-policy and --content-boundaries for untrusted sites. None is on by default, and the allowlist rejects --profile, --cdp and --restore
  5. Start MCP with agent-browser mcp, and add profiles such as --tools core,network only when needed

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, agent-browser or Playwright MCP?

Playwright MCP scores 67.6 (B) on agent readiness against agent-browser's 66.6 (B), and leads in 4 of 7 scored categories. agent-browser leads on schema & documentation and security & auth.

Do agent-browser and Playwright MCP need an API key?

Neither needs a key.

Can an agent call agent-browser and Playwright MCP without installing anything?

agent-browser runs on your own machine, with no hosted endpoint listed. Playwright MCP runs on your own machine, with no hosted endpoint listed.

Are agent-browser and Playwright MCP open source?

Yes. agent-browser is open source (Apache-2.0). Playwright MCP is open source (Apache-2.0).

Other comparisons with agent-browser 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.

Get an auditSee a sample report