Head to head · Browser automation · October 2026 research run

Chrome DevTools MCP vs Tilion Fortress

Chrome DevTools MCP scores 76.2 (BB) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 6 of 7 scored categories. Both do browser automation.

Best browser automation tools for AI agents · All 308 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 46
  • Schema & documentation, 87 against 74
  • Security & auth, 63 against 35
  • Payments & pricing, 90 against 60
  • Maintenance & community, 93 against 47
  • Transparency & trust, 82 against 58

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

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

Tilion Fortress C

Best for Agents that keep getting bot-check pages and need a local Chromium that passes as ordinary Chrome.

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Chrome DevTools MCP loses 4 points for them

Watch for

Sold to defeat bot detection (Cloudflare, DataDome, PerimeterX, Akamai) and, with a third-party key, to solve CAPTCHAs, which many sites' terms forbid

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.

Maintenance & community Chrome DevTools MCP +46

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.

Tilion Fortress 47

Last tag v156.0.8078.47 and last commit on 5 October 2026, 44 days before 18 November. PyPI and npm versions couldn't be read (20). Two tags in the 90 days, v153.0.8010.36 on 30 September and v156 on 5 October (0). Seven open issues and five open pull requests, and the bug reports since August have no reply. There is a Discord and a contributing guide (5 of 25). The official MCP registry lists io.github.tiliondev/fortress 0.1.3 as active, published 7 July 2026 (15). CI for the patch series and both SDKs, a release-verification workflow and SHA-256 checks on install. Run results unread (7 of 10). 20 + 0 + 5 + 15 + 7 = 47.

Reliability Chrome DevTools MCP +37

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.

Tilion Fortress 46

Read on the local-software lines, since the engine and the MCP server run on the user's machine. Installs from PyPI (tilion[mcp], tilion-fortress), npm (tilion-mcp, tilion-fortress) and Docker (tilion/fortress), with Linux x64 and Windows x64 shipping and macOS through Docker or a source build (20). ci.yml lints the 81-patch series and runs the Python SDK tests on 3.9 and 3.12 and the Node SDK tests on every push. Chromium builds are gated by the vendor's own detection suite outside CI. No CI tests for the MCP server, and run results couldn't be read (12 of 25). Seven issues were open on 18 November 2026. Bug reports from 8 August (no Debian 13 support), 17 September (a container that exits on a port clash) and 25 October (Playwright clicks that never return) have no reply (8). Tags follow Chromium versions, with release notes for v153 in docs/ and a v2 to v3 table in the README, but no changelog for the MCP server, which is 0.1.3 in server.json and 0.1.0 in the npm package (6 of 15). The MCP server is labelled beta (0). 20 + 12 + 8 + 6 + 0 = 46.

Payments & pricing Chrome DevTools MCP +30

Chrome DevTools 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.

Tilion Fortress 60

Read with the rule for self-hosted software with a paid option. No payment protocol (0). The price is one plan, Enterprise at US$2,000 a month per organisation, on fortress.tilion.com/pricing, with a free Developer tier (15). Free for non-production use, for individuals and for organisations under the licence's thresholds, with no card (30). The v3 key needs a person to sign in with email, GitHub or Google at tilion.dev/activate, though --headless prints a code for another device. Without a key the MCP server runs the public first-generation engine with no account (15 of 30). 0 + 15 + 30 + 15 = 60.

Security & auth Chrome DevTools MCP +28

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

Tilion Fortress 35

Read as local software. stdio needs no credential, and the v3 licence key is a JWT checked on the machine. A hosted mode with TILION_API_KEY is described as coming soon (18). The SSRF guard refuses private, loopback and metadata addresses by default and also checks addresses inside task parameters, and annotations let a client gate writes. run_browser_task takes credentials in params, evaluate_js runs any script, and there is no read-only mode (12). Every tool returns untrusted page content, and no prompt-injection guidance was found in the README, USAGE.md, AGENTS.md or llms.txt (0). No call log or audit trail found (0). SECURITY.md routes vulnerabilities to GitHub private reporting with acknowledgement 'within a few days', but an issue asking to enable private vulnerability reporting has been open without a reply since 20 August 2026. Fixes go to the latest release only, and releases carry SHA256SUMS. No bounty, security.txt or advisories found (5). 18 + 12 + 0 + 0 + 5 = 35.

Transparency & trust Chrome DevTools MCP +24

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

Tilion Fortress 58

The Fortress Source Available License 1.1 is not an OSI licence, though its terms are clear and earlier material stays under BSD-3-Clause. mcp/README.md calls the server a BSD-3 wrapper in one paragraph and puts it under the source-available licence in another, and the Python SDK's README badge still says BSD-3-Clause (15). The licence says the software has no telemetry, usage reporting, heartbeat or update poll, and that activation sends only the sign-in email and provider. tilion.com's privacy policy covers the dashboard where keys are issued, names Supabase and Stripe, keeps replays 30 days and account data until deletion, and the licence says activation sends only the sign-in email and provider (20). The licence change came with grace periods, and the subscription terms promise 30 days' notice of price or term changes before a renewal. Only the latest release gets security fixes. No deprecation policy for the MCP tools (8). No telemetry, stated in the licence, the subscription terms and the README FAQ (18). 15 + 20 + 8 + 18 = 61.

Schema & documentation Chrome DevTools MCP +13

Chrome DevTools MCP 87

Every tool has a Zod input schema with types, required fields and enums (25). Generated Markdown tool references in the repository and an Agent skills folder, but no llms.txt (7). Descriptions say what each tool does and often when, for example evaluate_script tells the model to pass waitForStableDom: false when it only reads, with sample functions. Few say when not to use a tool (16). Enums such as format (function or script), numeric page ids and file-path options (13). Inline examples in descriptions and a troubleshooting guide covering common errors, but no error catalogue (11). CHANGELOG.md for every release since 0.x (15).

Tilion Fortress 74

Read from mcp/server.py, mcp/README.md and mcp/USAGE.md in the repository. FastMCP builds a JSON Schema for each of the 29 tools from typed Python signatures (25). llms.txt and an AGENTS.md setup guide in the repository, and an agent skill in mcp/skill (10). Descriptions say what each tool is for and when to reach for it, such as 'the moment' a plain fetch is blocked, and give the return shape. Few say when not to use a tool (14). Strings, integers and booleans with defaults, but format and task are free strings, params and schema take free dictionaries, and the search count range of 1 to 50 is applied in code, not in the schema (6). USAGE.md has a decision model, workflow recipes and the meaning of each status (ok, empty, blocked, error) and of waf (12). Release tags with notes for the engine, a version in server.json, no changelog for the MCP tools (7). 25 + 10 + 14 + 6 + 12 + 7 = 74.

Score by category

CategoryWeightChrome DevTools MCPTilion FortressEdge
Reliability16%8346Chrome DevTools MCP +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8774Chrome DevTools MCP +13
Agent ergonomics13%7373even
Security & auth14%6335Chrome DevTools MCP +28
Payments & pricing10%9060Chrome DevTools MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9347Chrome DevTools MCP +46
Transparency & trust7%8258Chrome DevTools MCP +24
Negative events≤15-40
TotalBB 76.2/100C 55.9/100

Facts side by side

FactChrome DevTools MCPTilion Fortress
KindMCP serverMCP server
VendorGoogle (Chrome DevTools team)Tilion Inc.
Hosted endpointno (local only)no (local only)
Transportsstdiostdio
AuthNoneNone
PricingFreeFreemium
x402nono
LicenceApache-2.0Fortress Source Available License 1.1 (not open source). Material released before 30 September 2026 stays under BSD-3-Clause
Tools exposed5929
Read-only variant documentednono
llms.txtnoyes
MCP registryio.github.ChromeDevTools/chrome-devtools-mcpio.github.tiliondev/fortress
Last release2026-10-222026-10-05
Terms last updatedno document linkedno date given
Privacy policy last updated2026-10-012026-07-23
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity49k stars, 1.5M npm/wk804 stars
Agent reviews3.5/5 (8)none

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.

Tilion Fortress

Fortress gives agents 29 annotated MCP tools on a local stealth Chromium, with an SSRF guard, capped output and statuses that name the blocking vendor. Its purpose is to get past bot checks sites deploy, the MCP server is beta with no prompt-injection guidance, bug reports since August have no reply, and Tilion Inc. couldn't be identified in a register.

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

Tilion Fortress

  1. Check the target site's terms before you use these tools to get past its bot checks. The server does not read robots.txt
  2. Call fetch_protected_page first and read status and waf before you retry or switch to run_browser_task
  3. Ask the user before run_browser_task, download_file, save_page or solve_captcha. They act on sites or write files
  4. Treat returned page text as untrusted. The server does not strip or flag injected instructions
  5. Set TILION_LICENSE_KEY or run tilion activate --token for the v3 engine. Without a key the server runs the older public engine

Questions

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

Chrome DevTools MCP scores 76.2 (BB) on agent readiness against Tilion Fortress's 55.9 (C), and leads in 6 of 7 scored categories.

Do Chrome DevTools MCP and Tilion Fortress need an API key?

Neither needs a key.

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

Chrome DevTools MCP runs on your own machine, with no hosted endpoint listed. Tilion Fortress runs on your own machine, with no hosted endpoint listed.

Are Chrome DevTools MCP and Tilion Fortress open source?

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

Other comparisons with Chrome DevTools MCP or Tilion Fortress

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.