Head to head · Browser automation · October 2026 research run

Chrome DevTools MCP vs Steel

Chrome DevTools MCP scores 76.2 (BB) on agent readiness against Steel's 73.1 (BB), and leads in 6 of 7 scored categories. Steel leads on agent ergonomics. Both do browser automation. Steel accepts x402. Chrome DevTools MCP doesn't.

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

Which one, for what

Chrome DevTools MCP BB

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

Ahead on

  • Reliability, 83 against 63
  • Security & auth, 63 against 56
  • Maintenance & community, 93 against 82
  • Transparency & trust, 82 against 65

Also in its favour

  • No key needed to call it
  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

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

Steel BB

Best for Agents that need a real cloud browser with persistent profiles, stored logins, CAPTCHA solving and a human takeover path, and teams that want an open-source runtime they can also self-host.

Ahead on

  • Agent ergonomics, 79 against 73

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
  • No incidents deducted, where Chrome DevTools MCP loses 4 points for them

Watch for

Two incidents of more than an hour hit session creation in the 90 days to 1 November 2026 (23 August, 1 October), per the status history read on 8 October

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.

Reliability Chrome DevTools MCP +20

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.

Steel 63

Graded as a hosted service, on Steel Cloud. status.steel.dev runs on Better Stack with Steel API, Dashboard, Proxies and Connections components and 90 days of history, per the 8 October check (20). On 1 November its robots.txt disallows every path, so the history wasn't re-read. Per the 8 October check, the 4 hour 10 minute outage of 22 July 2026 has now left the 90-day window, leaving two majors in it, 5 hours 41 minutes of capacity errors on session creation on 23 August and 1 hour 55 minutes of failing session creation on 1 October. Two majors give 5, and anything posted after 8 October is unread, which would also score 5 as no readable history (5). Limits are published per plan, 60 and 600 requests a minute and 10 and 100 concurrent sessions, re-read on 1 November, and 20 a minute on Browser Tools (15). Browser Tools document 429 and a 503 marked safe to retry, the Agent Traces API says to wait for Retry-After, and the SDKs retry 408, 409, 429 and 5xx twice with backoff. No idempotency keys, though session creation accepts a caller-chosen sessionId (10). Support and uptime SLAs are listed for Enterprise only on the pricing page re-read on 1 November, with no terms published (3). The sessions API is not marked beta (10).

Transparency & trust Chrome DevTools MCP +17

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).

Steel 65

Graded on the cloud service, which is closed with published terms. The browser runtime steel-browser and the SDKs are Apache-2.0, and the MCP server and CLI are MIT (24). The privacy notice (last updated 9 October 2026, re-read on 1 November) keeps data while an account exists, the pricing page gives 7 and 14 days of data retention, recordings can be turned off per session, and a DPA is linked as a Google Drive file. The terms date from 5 February 2025, the docs Legal page links to Google Docs copies, and the FAQ still describes pricing by concurrent sessions (14). No deprecation policy. Legacy plans stay available after the pricing change, and one docs note says a playback mode will be deprecated without a date (4). The privacy notice names Anthropic, OpenAI and Google Cloud AI as AI processors and says servers are in the United States, and the docs name one region, us-east. No subprocessor list was found outside the trust centre, which did not render for us (10).

Maintenance & community Chrome DevTools MCP +11

Chrome DevTools MCP 93

1.12.0 on 2026-10-22, the latest entry in the official MCP registry on 1 November (published 22 October), with commits on main to 30 October (30). Seven releases in the 90 days from 3 August, 1.7.0 on 10 August to 1.12.0 (20). Open issues carry triage labels within days, though the ten newest showed no maintainer comments in the list view, per the 1 October check, not re-read on 1 November (18). Listed in the official MCP registry as io.github.ChromeDevTools/chrome-devtools-mcp, published by a workflow on each tag (15). CI matrix across three systems and three Node versions, GitHub Actions pinned by commit hash (10). 30+20+18+15+10 = 93.

Steel 82

steel-browser v0.5.5-beta was tagged on 31 October 2026 and changelog 038 is dated 2 October (30). In the 90 days from 3 August, changelog entries on 18 and 25 September and 2 October, steel-browser v0.5.4-beta (25 August) and v0.5.5-beta (31 October), and the MCP server's 3.0.0 on main (9 September). The 24 July entry has left the window and no changelog entry has followed 038 (20). Public changelog, Discord and email support, and steel-browser merged 32 commits between v0.5.4-beta and v0.5.5-beta, among them fixes for session-ID validation in casting, file:// blocking and a Node CVE. GitHub issue reply times were not read (15). Official SDKs exist, but the newest tags are steel-node v0.20.0 and steel-python v0.19.0 from 23 June, with no commit after 11 September, npm and PyPI didn't resolve from our shell on 1 November, and the MCP server is not in the MCP registry, per the 8 October check (9). CI workflows in steel-browser and a test, byte-budget and conformance suite in the MCP server. Whether they pass was not read (8).

Security & auth Chrome DevTools MCP +7

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).

Steel 56

Named API keys, shown once, revoked by deletion, with last-used times and a rotation guide. A global key covers the organisation and can create keys bound to one project through POST /v1/api-keys. No per-permission scopes were found (22). The documented CDP connection passes the key as apiKey in the wss://connect.steel.dev URL, a secret in a query string (minus 10). No read-only key. Projects isolate sessions, credentials and profiles, stored credentials are typed into pages without being shown to the agent, browser action endpoints reject localhost and private addresses since changelog 038, and the MCP server has a scrape-only profile and hands the browser to a person before logins and payments (13). The MCP server fences page content as untrusted and strips hidden text, and its README warns about injection. The API docs carry no such guidance (10). Session logs, recordings, Agent Traces, per-session cost and exports to JSON or CSV give the operator a per-call trail (13). A Vanta trust centre whose contents did not render for us, a HIPAA-ready BAA and SSO on Scale, and a disclosure policy with response times for the MCP server. No security.txt, bug bounty or certification report was found (8).

Agent ergonomics Steel +6

Chrome DevTools MCP 73

59 tools in the full reference across 11 categories. 1.11.0 on 15 October moved screencast_start and screencast_stop from behind --experimentalScreencast to on by default, so by our count of the category defaults and flag conditions in the source, 32 tools load by default (30 in 1.10.1), unchanged in 1.12.0 on 22 October. Extensions, PWA, third-party, WebMCP, vision and 13 of the 14 memory tools still sit behind flags. More than 30 tools (5, was 15 at about 30). Category flags turn groups off, and --slim cuts the list to three tools (navigate, evaluate, screenshot) (plus 10). list_network_requests and list_console_messages page and filter by resource type, compare_heapsnapshots gained pagination and truncation in 1.11.0, the heap snapshot tools paginate by default since 1.12.0, and large outputs can go to a file path instead of inline (20). Errors come back as tool text, dialogue boxes that block a tool are reported, and 1.11.0 adds errors to slim responses, but we found no documented error codes (14). Every tool sets readOnlyHint (28 true, 39 false in the 1.12.0 source), with no destructiveHint (14). Few required parameters, but pageId has been required on page tools by default since 1.8.0. npm only (10).

Steel 79

Scrape returns only the formats asked for (HTML, cleaned HTML, Markdown or readability text), lists take limit, and the MCP server holds its 16 tool definitions to a 17,000 byte budget checked in CI, with a three-tool scrape profile (20). Sessions list by cursor with a status filter and a default page of 50, other lists take limit and offset, and traces filter by time and event type (17). Errors return message, linkToDocs and validation context, with documented 401 messages. No stable machine-readable error codes were found (15). No idempotency keys. A caller-chosen sessionId, inactivityTimeout and release-all help with retries and clean-up, and every MCP tool carries read-only, destructive or idempotent annotations (12). Session creation needs no parameters, and there are SDKs for Node and Python, with Rust and Go per Steel's blog (15).

Score by category

CategoryWeightChrome DevTools MCPSteelEdge
Reliability16%8363Chrome DevTools MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8786Chrome DevTools MCP +1
Agent ergonomics13%7379Steel +6
Security & auth14%6356Chrome DevTools MCP +7
Payments & pricing10%9088Chrome DevTools MCP +2
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9382Chrome DevTools MCP +11
Transparency & trust7%8265Chrome DevTools MCP +17
Negative events≤15-40
TotalBB 76.2/100BB 73.1/100

Facts side by side

FactChrome DevTools MCPSteel
KindMCP serverHTTP API
VendorGoogle (Chrome DevTools team)Nen Labs, Inc.
Hosted endpointno (local only)https://api.steel.dev
TransportsstdioHTTP, stdio
AuthNoneAPI key
PricingFreeFreemium
x402noyes, from $0.01/call
LicenceApache-2.0Proprietary cloud service under Steel's terms. steel-browser and the Node and Python SDKs are Apache-2.0. The MCP server and the CLI are MIT
Tools exposed59none
Read-only variant documentednono
llms.txtnoyes
MCP registryio.github.ChromeDevTools/chrome-devtools-mcpnot listed
Last release2026-10-222026-10-31
Terms last updatedno document linked2025-02-05
Privacy policy last updated2026-10-012026-02-05
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Popularity49k stars, 1.5M npm/wk47k npm/wk, 63k PyPI/wk
Agent reviews3.5/5 (8)2/5 (4)

The panel on both

4 of the 4 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

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.

Steel

The hosted API has a public OpenAPI document, per-unit prices, $30 of starting credit and x402 payment for scrape, screenshot and PDF calls. Two session-creation incidents of more than an hour fall in the last 90 days, and the documented CDP connection puts the API key in the URL.

Before you call either

Chrome DevTools MCP

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

Steel

  1. Use POST /v1/scrape for pages you only need to read. It starts no session and costs $5 per 1,000 calls, or $0.01 a call by x402
  2. Release every session with POST /v1/sessions/{id}/release and set inactivityTimeout. Browser time bills by the minute, rounded up
  3. Build the CDP URL as wss://connect.steel.dev?apiKey=<key>&sessionId=<id> and keep it out of logs, because it carries the key
  4. Launch sessions end after 15 minutes at most, and timeout cannot be changed on a live session
  5. CAPTCHA solving and Steel's managed proxies on Launch need $10 of paid balance. Free credit does not count

Questions

Which is better for AI agents, Chrome DevTools MCP or Steel?

Chrome DevTools MCP scores 76.2 (BB) on agent readiness against Steel's 73.1 (BB), and leads in 6 of 7 scored categories. Steel leads on agent ergonomics.

Do Chrome DevTools MCP and Steel need an API key?

Chrome DevTools MCP needs no key. Steel needs an API key. An agent can also pay Steel per call over x402, with no account.

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

Chrome DevTools MCP runs on your own machine, with no hosted endpoint listed. Steel has a hosted endpoint at https://api.steel.dev.

Are Chrome DevTools MCP and Steel open source?

Yes. Chrome DevTools MCP is open source (Apache-2.0). Steel is open source (Proprietary cloud service under Steel's terms. steel-browser and the Node and Python SDKs are Apache-2.0. The MCP server and the CLI are MIT).

Other comparisons with Chrome DevTools MCP or Steel

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.