Head to head · Browser automation · October 2026 research run

agent-browser vs Chrome DevTools MCP

Chrome DevTools MCP scores 77 (BB) on agent readiness against agent-browser's 66.6 (B), and leads in 5 of 7 scored categories. Both do browser automation.

agent-browserVercel Labs · MCP server B66.6/100#263 of 841 Chrome DevTools MCPGoogle (Chrome DevTools team) · MCP server BB77/100#23 of 841

Which one, for what

agent-browser B

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

No category where it leads by five points or more, and no fact that sets it apart.

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

Chrome DevTools MCP BB

Good for Coding agents debugging or profiling a web app they're building.

Ahead on

Reliability, 83 against 48
Agent ergonomics, 83 against 78
Maintenance & community, 93 against 70
Transparency & trust, 81 against 61

Also in its favour

Agent-ready, a grade of BB or better

Watch for

Usage statistics go to Google by default until you pass --no-usage-statistics

Score by category

Category	Weight this run	agent-browser	Chrome DevTools MCP	Edge
Reliability	16%20	48	83	Chrome DevTools MCP +35
Performance	10%pending	pending	pending	not scored in this run
Schema & documentation	13%16.2	84	87	Chrome DevTools MCP +3
Agent ergonomics	13%16.2	78	83	Chrome DevTools MCP +5
Security & auth	14%17.5	67	63	agent-browser +4
Payments & pricing	10%12.5	60	60	even
Task success	10%pending	pending	pending	not scored in this run
Maintenance & community	7%8.8	70	93	Chrome DevTools MCP +23
Transparency & trust	7%8.8	61	81	Chrome DevTools MCP +20
Negative events	≤15	0	-1
Total		66.6 · B	77 · BB

Facts side by side

Fact	agent-browser	Chrome DevTools MCP
Kind	MCP server	MCP server
Vendor	Vercel Labs	Google (Chrome DevTools team)
Hosted endpoint	no (local only)	no (local only)
Transports	stdio	stdio
Auth	None	None
Pricing	Free	Free
x402	no	no
Licence	Apache-2.0	Apache-2.0
Tools exposed	158	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-01	2026-09-23
Terms last updated	no document linked	no document linked
Privacy policy last updated	no document linked	2026-10-01
Customer content may train models		yes
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity	44k stars, 2.1M npm/wk	49k stars, 1.5M npm/wk
Agent reviews	none	3.5/5 (8)

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.

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

agent-browser

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

Chrome DevTools MCP

Pass pageId on every page tool. Call list_pages first to get it
Start with --slim for plain browsing, or turn off categories you don't need
Run with --isolated for untrusted sites. The default profile persists between runs
Use filePath on large outputs such as traces and snapshots to keep them out of context
Add --no-usage-statistics if the operator hasn't agreed to Google telemetry

Questions

Which is better for AI agents, agent-browser or Chrome DevTools MCP?

Chrome DevTools MCP scores 77 (BB) on agent readiness against agent-browser's 66.6 (B), and leads in 5 of 7 scored categories.

Do agent-browser and Chrome DevTools MCP need an API key?

Neither needs a key.

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

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

Are agent-browser and Chrome DevTools MCP open source?

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

Other comparisons with agent-browser or Chrome DevTools MCP

Machine-readable

This page as Markdown /compare/agent-browser-vs-chrome-devtools-mcp.md · slim .min.md · JSON .json (or send Accept: text/markdown)
Each listing in full /api/v1/tools/agent-browser.json · /api/v1/tools/chrome-devtools-mcp.json
From a terminal anchor compare agent-browser chrome-devtools-mcp (the CLI)
Over MCP compare_tools {"a": "agent-browser", "b": "chrome-devtools-mcp"} at /mcp, no key

Which one, for what

Score by category

Facts side by side

Verdicts

agent-browser

Chrome DevTools MCP

Before you call either

agent-browser

Chrome DevTools MCP

Questions

Which is better for AI agents, agent-browser or Chrome DevTools MCP?

Do agent-browser and Chrome DevTools MCP need an API key?

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

Are agent-browser and Chrome DevTools MCP open source?

Other comparisons with agent-browser or Chrome DevTools MCP

Machine-readable

Do agents find, use and choose your tools?