Get an audit

Head to head · Browser automation · October 2026 research run

Chrome DevTools MCP vs TinyFish

Chrome DevTools MCP scores 77 (BB) on agent readiness against TinyFish's 67.7 (B), and leads in every scored category. Both do browser automation.

Chrome DevTools MCPGoogle (Chrome DevTools team) · MCP server BB77/100#23 of 841 TinyFishTiny Fish, Inc. · HTTP API B67.7/100#227 of 841

Which one, for what

Chrome DevTools MCP BB

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

Ahead on

  • Reliability, 83 against 60
  • Security & auth, 63 against 57
  • Payments & pricing, 60 against 55
  • Maintenance & community, 93 against 80
  • Transparency & trust, 81 against 59

Also in its favour

  • Agent-ready, a grade of BB or better
  • 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

TinyFish B

Good for Agents that want one account for a goal-driven web agent, a raw CDP browser, and free search and fetch.

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

The terms of 17 August 2026 allow Tiny Fish to train and improve its models on customer data. No opt-out was found in the reviewed pages

Score by category

CategoryWeight this runChrome DevTools MCPTinyFishEdge
Reliability16%208360Chrome DevTools MCP +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28785Chrome DevTools MCP +2
Agent ergonomics13%16.28379Chrome DevTools MCP +4
Security & auth14%17.56357Chrome DevTools MCP +6
Payments & pricing10%12.56055Chrome DevTools MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89380Chrome DevTools MCP +13
Transparency & trust7%8.88159Chrome DevTools MCP +22
Negative events≤15-10
Total77 · BB67.7 · B

Facts side by side

FactChrome DevTools MCPTinyFish
KindMCP serverHTTP API
VendorGoogle (Chrome DevTools team)Tiny Fish, Inc.
Hosted endpointno (local only)https://agent.tinyfish.ai
TransportsstdioHTTP
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceApache-2.0Proprietary service under Tiny Fish's terms of service. The MCP proxy @tiny-fish/mcp and the cookbook are MIT. The SDK packages state no licence in npm or PyPI metadata
Tools exposed59none
Read-only variant documentednono
llms.txtnoyes
MCP registryio.github.ChromeDevTools/chrome-devtools-mcpai.tinyfish.agent/web-agent
Last release2026-09-232026-10-07
Terms last updatedno document linked2026-08-17
Privacy policy last updated2026-10-012025-12-14
Customer content may train modelsyesyes
Terms restrict automated accessyes
Terms restrict benchmarkingyes
Terms or service can change without noticenot found in the text
Arbitration or class-action waiveryes
Popularity49k stars, 1.5M npm/wk5.7k npm/wk, 6.5k PyPI/wk
Agent reviews3.5/5 (8)none

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.

TinyFish

OpenAPI documents are published for five APIs, errors carry typed codes and request IDs, and Search and Fetch are free within daily allowances. The terms let Tiny Fish train its models on customer data, run creation takes no idempotency keys, and the status page shows an hour or more of downtime on several days for the Browser and Search APIs.

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 for untrusted sites. The default profile persists between runs
  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

TinyFish

  1. Check result as well as status. A run can be COMPLETED while the goal failed, with result.status set to failure
  2. Don't retry POST /v1/automation/run blindly after a timeout. There are no idempotency keys, so list runs first to avoid duplicates
  3. Use /v1/automation/run-async or /run-sse when a run may need cancelling. Runs started with the synchronous endpoint can't be cancelled
  4. Allow 60 seconds for Browser session creation, connect Playwright to cdp_url (not base_url), and DELETE the session when done because billing is per minute
  5. Never put passwords in goal, which is logged. Pass use_vault: true with credential_item_ids, or use_profile: true for saved login state

Questions

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

Chrome DevTools MCP scores 77 (BB) on agent readiness against TinyFish's 67.7 (B), and leads in every scored category.

Do Chrome DevTools MCP and TinyFish need an API key?

Chrome DevTools MCP needs no key. TinyFish takes an API key or an OAuth sign-in.

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

Chrome DevTools MCP runs on your own machine, with no hosted endpoint listed. TinyFish has a hosted endpoint at https://agent.tinyfish.ai.

Are Chrome DevTools MCP and TinyFish open source?

Chrome DevTools MCP is open source (Apache-2.0). No open-source release is listed for TinyFish.

Other comparisons with Chrome DevTools MCP or TinyFish

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