{ "data": { "a": { "slug": "autocua", "name": "AutoCua", "vendor": "Ashish Yadav and contributors (ComputerUseAgent on GitHub)", "vendorUrl": "https://github.com/ComputerUseAgent/AutoCua", "kind": "framework", "category": "desktop-automation", "summary": "AutoCua is an open-source Python agent that operates a computer the way a person does, desktop apps, a terminal, your own Chrome and iOS or Android phones, with any of 60 models from ten providers.", "url": "https://www.anchorterminal.com/tools/autocua", "markdownUrl": "https://www.anchorterminal.com/tools/autocua.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/autocua.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/autocua.json", "dns": "autocua.grade.anchorterminal.com", "repo": "https://github.com/ComputerUseAgent/AutoCua", "license": "MIT", "transports": [], "packages": [ { "registry": "pypi", "name": "AutoCua" } ], "auth": "none", "authNotes": "No account. You bring an API key for the model provider you choose, kept with chats, Chrome profiles and a credential vault in a local AutoCua_data folder.", "pricing": "free", "pricingNotes": "Free and MIT-licensed. You pay your model provider for tokens. Nothing to buy from the project (checked 2026-11-06).", "priceSummary": "Free · OSS", "where": "library", "x402": { "level": "no", "evidence": "A local package with nothing to buy and no payment protocol (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://github.com/ComputerUseAgent/AutoCua#readme", "capabilities": [ "browser.control", "agent.run" ], "tags": [ "open-source", "mit", "python", "computer-use", "local", "new" ], "lastRelease": "2026-11-04", "graded": true, "anchor": { "graded": true, "score": 44.3, "grade": "E", "agentReady": false, "rank": 1100, "ranked": true, "rankOf": 1354, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 55, "maintenance": 65, "payments": 60, "reliability": 25, "schema": 42, "security": 38, "transparency": 42 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-06" }, "negative": 0, "verdict": "A capable, fast-moving open-source agent for driving desktops, browsers and phones through real input and accessibility trees, with a careful safety section. It's two weeks old, with no test CI or changelog, and on Windows the model itself decides whether to accept an admin elevation prompt.", "bestFor": "Developers who want a local agent to operate desktop apps, their own browser or phones across platforms, on a machine they control.", "strengths": [ "One run_agent call drives the desktop, a terminal, your Chrome, or an iOS or Android device", "Element picking from accessibility trees and OCR instead of pixel coordinates", "Credentials typed from a vault so the model never sees them, in the browser and phone agents", "No telemetry, and nothing downloaded without a yes on the terminal", "MIT licence, a pip wheel per OS and architecture, and 60 models across ten providers" ], "weaknesses": [ "Two weeks old at version 0.1.9, with no changelog file", "No CI running the tests; the only workflow labels issues", "On Windows the model answers UAC elevation prompts itself through a kernel input driver", "Keeps API keys and logged-in Chrome profiles in a local folder next to the checkout", "No API reference beyond the README" ], "agentNotes": [ "pip install AutoCua, then call run_agent with a mode such as \"web use\" or \"computer use\", a provider, a model and a task", "Run it on a machine or account you can afford to lose; it drives real input and keeps logged-in browser profiles", "On Windows, don't install the Interception driver unless you accept the model deciding UAC prompts", "Set AutoCua_DATA_DIR to keep keys and profiles somewhere private", "Phones go over USB from a script; Wi-Fi only through the desktop app" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 44.3 } ], "editorialScores": { "ergonomics": 55, "maintenance": 65, "payments": 60, "reliability": 25, "schema": 42, "security": 38, "transparency": 70 }, "provenanceScore": 13, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install AutoCua\n# then, in Python:\n# from AutoCua.agent_launcher import run_agent\n# run_agent(mode=\"web use\", provider=\"openrouter\", model=\"gemini-3.8-flash\", task=\"Open wikipedia.org and summarise today's featured article.\")" }, "letme": { "capability": "https://letme.dev/browser.control", "tool": "https://letme.dev/autocua" }, "area": "developer", "provenance": { "legalEntity": "", "domain": "github.com", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The licence names Ashish Yadav as copyright holder; most commits are from the GitHub user FunctionFreak. No company, site or terms were found.", "github.com/AutoCua/AutoCua and github.com/ComputerUseAgent/AutoCua serve the same main branch, so one is a rename or mirror of the other." ], "score": 13 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/autocua.json" }, "answer": "Chrome DevTools MCP scores 72.4 (BB) on agent readiness against AutoCua's 44.3 (E), and leads in 6 of 7 scored categories.", "b": { "slug": "chrome-devtools-mcp", "name": "Chrome DevTools MCP", "vendor": "Google (Chrome DevTools team)", "vendorUrl": "https://developer.chrome.com/docs/devtools", "kind": "mcp", "category": "browser", "summary": "Lets coding agents control and inspect a live Chrome instance.", "url": "https://www.anchorterminal.com/tools/chrome-devtools-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/chrome-devtools-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/chrome-devtools-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/chrome-devtools-mcp.json", "dns": "chrome-devtools-mcp.grade.anchorterminal.com", "repo": "https://github.com/ChromeDevTools/chrome-devtools-mcp", "license": "Apache-2.0", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "chrome-devtools-mcp" } ], "auth": "none", "authNotes": "Local process; supports custom WebSocket headers when attaching to an authenticated remote Chrome endpoint.", "pricing": "free", "pricingNotes": "Open source; no hosted service.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No payments. Local open-source server.", "endpoints": [] }, "toolCount": 59, "popularity": { "githubStars": 49300, "npmWeekly": 1500288, "pypiWeekly": null, "asOf": "2026-09-26" }, "docsUrl": "https://github.com/ChromeDevTools/chrome-devtools-mcp#readme", "registryName": "io.github.ChromeDevTools/chrome-devtools-mcp", "capabilities": [ "browser.control", "browser.debug" ], "tags": [ "official", "local", "open-source", "browser", "devtools" ], "lastRelease": "2026-10-22", "graded": true, "anchor": { "graded": true, "score": 72.4, "grade": "BB", "agentReady": true, "rank": 112, "ranked": true, "rankOf": 1354, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 93, "payments": 60, "reliability": 83, "schema": 87, "security": 63, "transparency": 82 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-01" }, "negative": -4, "negativeNotes": [ "-1: two moderate advisories published by the maintainers, GHSA-3pvj-jv98-qhjq on 2026-06-15 (daemon.pid written through symlinks in the /tmp fallback directory) and GHSA-8qf9-62x2-82pp on 2026-06-16 (path validation not canonicalising symlinks before enforcing roots). Fixed and disclosed in public, so a small deduction (https://github.com/ChromeDevTools/chrome-devtools-mcp/security/advisories).", "-3: 2026-08-25. 1.8.0, a minor release, made `pageId` required on page-scoped tools by default (page ID routing had been off by default behind `--experimentalPageIdRouting` in 1.7.0), so a client calling page tools without it fails validation. The changelog files it as a new capability with no breaking label, and no earlier notice was found. `--no-page-id-routing` restores the old behaviour, so 3 points, the floor, by the 1 November 2026 rule for breaking changes in a minor release, as zenrows and docker-agent were read (https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/CHANGELOG.md)." ], "verdict": "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`.", "bestFor": "Coding agents debugging or profiling a web app they're building.", "strengths": [ "Performance traces, network inspection, heap snapshots and Lighthouse audits in one server", "Every tool carries `readOnlyHint`, and category flags and `--slim` cut the tool list from about 32 to three", "`--javascript-evaluation false`, URL allow and block patterns and MCP roots for least privilege", "Seven releases in the 90 days to 1 November 2026, the newest 1.12.0 on 22 October, CI on three systems and three Node versions, listed in the official MCP registry", "Reports go through Google's open-source vulnerability reward programme, and two advisories were published in public in 2026" ], "weaknesses": [ "Usage statistics go to Google by default until you pass `--no-usage-statistics`", "`--isolated` and network header redaction are off by default, so the agent sees a persistent profile and raw headers", "1.8.0 made `pageId` required on page tools in a minor release with no notice, and 1.11.0 put two more tools in the default list", "SECURITY.md treats prompt injection from page content as the client's problem", "No `destructiveHint` on any tool, though 39 of 67 annotations mark tools as not read-only" ], "agentNotes": [ "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` and `--file-navigations` for untrusted sites. The default profile persists between runs and file: URLs are allowed", "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" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 8, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.4 } ], "editorialScores": { "ergonomics": 73, "maintenance": 93, "payments": 60, "reliability": 83, "schema": 87, "security": 63, "transparency": 76 }, "provenanceScore": 87, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest", "config": { "mcpServers": { "chrome-devtools": { "args": [ "-y", "chrome-devtools-mcp@latest" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/browser.control", "tool": "https://letme.dev/chrome-devtools-mcp" }, "sameCompany": [ "gemini-api", "gemini-embedding", "vertex-ai-tuning", "google-model-armor", "google-imagen", "google-veo", "google-lyria", "google-speech-to-text", "gemini-live", "google-adk", "google-secret-manager", "google-cloud-document-ai", "google-weather-api", "google-maps-platform", "google-cloud-translation", "google-calendar-api", "firebase-cloud-messaging", "google-drive-api", "gemini-enterprise", "gemini-cli", "google-search-console", "google-ads-api", "google-forms", "google-sheets-api", "gmail-api", "google-people-api" ], "area": "developer", "provenance": { "legalEntity": "Google LLC", "domain": "google.com", "domainRegistered": "1997-09-15", "domainNote": "Published by Google under the ChromeDevTools organisation on GitHub.", "endpointOnVendorDomain": null, "terms": "", "privacy": "https://policies.google.com/privacy", "statusPage": "", "changelog": "https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/CHANGELOG.md", "securityTxt": "valid", "checked": "2026-09-26", "score": 87 }, "requirements": { "agentAlone": true, "card": "no", "freeTier": true, "credential": "none", "hosting": [ "self-hosted" ], "euResidency": "unknown", "trainsOnData": "no", "zeroRetention": "unknown", "selfHost": "yes" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/chrome-devtools-mcp.json", "live": { "slug": "chrome-devtools-mcp", "versions": [ { "registry": "github", "name": "ChromeDevTools/chrome-devtools-mcp", "version": "chrome-devtools-mcp-v1.12.0", "released": "2026-10-22", "seenAt": "2026-11-05T21:20:15.83126538Z" }, { "registry": "mcp-registry", "name": "io.github.ChromeDevTools/chrome-devtools-mcp", "version": "1.12.0", "seenAt": "2026-11-05T17:32:31.346782632Z" }, { "registry": "npm", "name": "chrome-devtools-mcp", "version": "1.12.0", "seenAt": "2026-11-05T21:20:15.177839224Z" } ], "githubStars": 54847, "npmWeekly": 1852001, "securityTxt": { "url": "https://google.com/.well-known/security.txt", "state": "valid", "expires": "2030-04-01T00:00:00z", "checkedAt": "2026-11-05T15:56:23.105160367Z" }, "domain": { "domain": "google.com", "registered": "1997-09-15", "source": "https://rdap.verisign.com/com/v1/domain/google.com", "checkedAt": "2026-11-01T14:17:18.719851913Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/ChromeDevTools/chrome-devtools-mcp/main/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-05T13:02:35.899011863Z", "changedAt": "2026-10-23T01:54:24.65852137Z", "fingerprint": "d2bd6383f283" }, { "url": "https://raw.githubusercontent.com/ChromeDevTools/chrome-devtools-mcp/main/docs/configuration.md", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-05T13:02:37.922901567Z", "changedAt": "2026-11-05T13:02:37.922901567Z", "fingerprint": "27b8487b4cb4" }, { "url": "https://policies.google.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:43:37.926236649Z", "changedAt": "2026-10-02T15:23:08.649962611Z", "fingerprint": "5d0b010ca1ea" } ], "github": { "repo": "chromedevtools/chrome-devtools-mcp", "checkedAt": "2026-11-02T08:38:32.052833068Z", "stars": 54641, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T05:22:22Z", "openIssues": 82, "openPRs": 50, "issuesOpened90d": 217, "issuesClosed90d": 212, "prsMerged90d": 503, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-30T10:15:16Z" }, "advisories": [ { "ghsa": "GHSA-5hw5-4q87-m6x9", "severity": "medium", "published": "2026-10-22T12:14:59Z" }, { "ghsa": "GHSA-xfxg-8r4q-wj4v", "severity": "medium", "published": "2026-10-22T12:14:35Z" }, { "ghsa": "GHSA-8qf9-62x2-82pp", "cve": "CVE-2026-53766", "severity": "medium", "published": "2026-06-16T15:13:35Z" }, { "ghsa": "GHSA-3pvj-jv98-qhjq", "cve": "CVE-2026-53765", "severity": "medium", "published": "2026-06-15T08:44:04Z" } ], "replies": { "sampled": 25, "unanswered": 6, "medianDays": 0.3 } }, "updatedAt": "2026-11-05T21:20:15.83126538Z" } }, "edges": [ { "by": 58, "category": "reliability", "leads": "chrome-devtools-mcp", "name": "Reliability", "reasons": { "a": "Local package. Installs from PyPI as AutoCua with Python 3.10 or later and the supported platforms stated (20). No CI runs the tests; the only workflow, use_case_label.yml, labels issues (0). GitHub issues weren't read, so the open-issue line is scored absent (0). Four tags in a week with no changelog file (5). Version 0.1.9 (0). 20 + 0 + 0 + 5 + 0 = 25.", "b": "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." }, "scores": { "a": 25, "b": 83 } }, { "by": 45, "category": "schema", "leads": "chrome-devtools-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "Framework reading. No API reference or typed interface beyond run_agent's documented arguments (5 of 25). No llms.txt (0). The README says what each mode drives and where it runs, and agent_capabilities.md lists what it can do (16 of 20). Modes and device are documented strings (6 of 15). Many examples, no documented errors (10 of 15). Tags without a changelog (5 of 15). 5 + 0 + 16 + 6 + 10 + 5 = 42.", "b": "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)." }, "scores": { "a": 42, "b": 87 } }, { "by": 40, "category": "transparency", "leads": "chrome-devtools-mcp", "name": "Transparency \u0026 trust", "reasons": { "a": "MIT (30). Says it sends data only to the chosen model provider and keeps everything else locally, and the source agrees (20 of 30). No deprecation policy (0). States no telemetry, and none was found (20). 30 + 20 + 0 + 20 = 70.", "b": "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)." }, "scores": { "a": 42, "b": 82 } }, { "by": 28, "category": "maintenance", "leads": "chrome-devtools-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "v0.1.9 tagged on 4 November 2026 (30). Four tags in 90 days (20). Issues and pull requests weren't read (0 of 25). The PyPI wheel is current (15). No CI; dependencies pinned per OS in requirements files (0 of 10). 30 + 20 + 0 + 15 + 0 = 65.", "b": "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." }, "scores": { "a": 65, "b": 93 } }, { "by": 25, "category": "security", "leads": "chrome-devtools-mcp", "name": "Security \u0026 auth", "reasons": { "a": "Framework reading (telemetry, approvals, guardrails, sandboxing). Provider keys stored in a local folder with Chrome profiles (10 of 30). The worker tools are an allow-list with no write tool, unseen ids are refused, downloads need a yes, but on Windows the model answers UAC elevation prompts itself through a kernel driver, with no person asked (6 of 20). The scraping ruleset has a prompt-injection instruction to log page text that gives instructions (10 of 15). Runs are logged in the app, with no audit log (7 of 15). No security policy, disclosure route or advisories found (5 of 20, for the vault and certificate handling). 10 + 6 + 10 + 7 + 5 = 38.", "b": "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)." }, "scores": { "a": 38, "b": 63 } }, { "by": 18, "category": "ergonomics", "leads": "chrome-devtools-mcp", "name": "Agent ergonomics", "reasons": { "a": "Framework reading. One call with a mode, provider, model and task runs a whole agent (20 of 25). A separate compression agent splices handoff summaries in, and runs are capped and stoppable (15 of 20). Permission and blocked-input errors are reported specifically, with no error reference (8 of 20). No resume or retry semantics described (2 of 20). Sensible defaults (simulators unless device is set), Python only (10 of 15). 20 + 15 + 8 + 2 + 10 = 55.", "b": "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)." }, "scores": { "a": 55, "b": 73 } } ], "facts": [ { "a": "Agent framework", "b": "MCP server", "name": "Kind" }, { "a": "Ashish Yadav and contributors (ComputerUseAgent on GitHub)", "b": "Google (Chrome DevTools team)", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "stdio", "name": "Transports" }, { "a": "None", "b": "None", "name": "Auth" }, { "a": "Free", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "Apache-2.0", "name": "Licence" }, { "a": "none", "b": "59", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.ChromeDevTools/chrome-devtools-mcp", "name": "MCP registry" }, { "a": "2026-11-04", "b": "2026-10-22", "name": "Last release" }, { "a": "no document linked", "b": "no document linked", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-10-01", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "yes", "name": "Customer content may train models" }, { "a": "none", "b": "49k stars, 1.5M npm/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (8)", "name": "Agent reviews" } ], "faq": [ { "answer": "Chrome DevTools MCP scores 72.4 (BB) on agent readiness against AutoCua's 44.3 (E), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, AutoCua or Chrome DevTools MCP?" }, { "answer": "No hosted endpoint is listed for AutoCua. Chrome DevTools MCP runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call AutoCua and Chrome DevTools MCP without installing anything?" }, { "answer": "Yes. AutoCua is open source (MIT). Chrome DevTools MCP is open source (Apache-2.0).", "question": "Are AutoCua and Chrome DevTools MCP open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No incidents deducted, where Chrome DevTools MCP loses 4 points for them" ], "goodFor": "Developers who want a local agent to operate desktop apps, their own browser or phones across platforms, on a machine they control.", "slug": "autocua", "watchFor": "Two weeks old at version 0.1.9, with no changelog file" }, { "aheadOn": [ "Reliability, 83 against 25", "Schema \u0026 documentation, 87 against 42", "Agent ergonomics, 73 against 55", "Security \u0026 auth, 63 against 38", "Maintenance \u0026 community, 93 against 65", "Transparency \u0026 trust, 82 against 42" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine" ], "goodFor": "Coding agents debugging or profiling a web app they're building.", "slug": "chrome-devtools-mcp", "watchFor": "Usage statistics go to Google by default until you pass `--no-usage-statistics`" } ], "history": { "autocua": null, "chrome-devtools-mcp": [ { "causes": [ "correction" ], "date": "2026-11-01", "delta": -3, "from": 75.4, "fromGrade": "BB", "to": 72.4, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-28", "delta": 0, "from": 75.4, "fromGrade": "BB", "to": 75.4, "toGrade": "BB" }, { "causes": [ "product" ], "date": "2026-10-17", "delta": -1.6, "from": 77, "fromGrade": "BB", "to": 75.4, "toGrade": "BB" } ] }, "job": { "capability": "browser.control", "name": "Browser automation" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agent-browser-vs-autocua.json", "title": "agent-browser vs AutoCua", "url": "https://www.anchorterminal.com/compare/agent-browser-vs-autocua" }, { "json": "https://www.anchorterminal.com/compare/agent-browser-vs-chrome-devtools-mcp.json", "title": "agent-browser vs Chrome DevTools MCP", "url": "https://www.anchorterminal.com/compare/agent-browser-vs-chrome-devtools-mcp" }, { "json": "https://www.anchorterminal.com/compare/airtop-vs-autocua.json", "title": "Airtop vs AutoCua", "url": "https://www.anchorterminal.com/compare/airtop-vs-autocua" }, { "json": "https://www.anchorterminal.com/compare/airtop-vs-chrome-devtools-mcp.json", "title": "Airtop vs Chrome DevTools MCP", "url": "https://www.anchorterminal.com/compare/airtop-vs-chrome-devtools-mcp" }, { "json": "https://www.anchorterminal.com/compare/anchor-browser-vs-autocua.json", "title": "Anchor Browser vs AutoCua", "url": "https://www.anchorterminal.com/compare/anchor-browser-vs-autocua" }, { "json": "https://www.anchorterminal.com/compare/anchor-browser-vs-chrome-devtools-mcp.json", "title": "Anchor Browser vs Chrome DevTools MCP", "url": "https://www.anchorterminal.com/compare/anchor-browser-vs-chrome-devtools-mcp" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-browser-use.json", "title": "AutoCua vs Browser Use", "url": "https://www.anchorterminal.com/compare/autocua-vs-browser-use" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-browserless.json", "title": "AutoCua vs Browserless", "url": "https://www.anchorterminal.com/compare/autocua-vs-browserless" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-bx-playwright.json", "title": "AutoCua vs BxPlaywright", "url": "https://www.anchorterminal.com/compare/autocua-vs-bx-playwright" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-functionize-mcp.json", "title": "AutoCua vs Functionize MCP server", "url": "https://www.anchorterminal.com/compare/autocua-vs-functionize-mcp" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-hyperbrowser.json", "title": "AutoCua vs Hyperbrowser", "url": "https://www.anchorterminal.com/compare/autocua-vs-hyperbrowser" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-kane-cli.json", "title": "AutoCua vs Kane CLI", "url": "https://www.anchorterminal.com/compare/autocua-vs-kane-cli" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-lightpanda.json", "title": "AutoCua vs Lightpanda", "url": "https://www.anchorterminal.com/compare/autocua-vs-lightpanda" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-notte.json", "title": "AutoCua vs Notte", "url": "https://www.anchorterminal.com/compare/autocua-vs-notte" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-playwright-mcp.json", "title": "AutoCua vs Playwright MCP", "url": "https://www.anchorterminal.com/compare/autocua-vs-playwright-mcp" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-pomerado.json", "title": "AutoCua vs Pomerado", "url": "https://www.anchorterminal.com/compare/autocua-vs-pomerado" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-puppeteer.json", "title": "AutoCua vs Puppeteer", "url": "https://www.anchorterminal.com/compare/autocua-vs-puppeteer" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-puppeteer-reference-server-archived.json", "title": "AutoCua vs Puppeteer (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/autocua-vs-puppeteer-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-robocorp.json", "title": "AutoCua vs Robocorp", "url": "https://www.anchorterminal.com/compare/autocua-vs-robocorp" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-selenium.json", "title": "AutoCua vs Selenium", "url": "https://www.anchorterminal.com/compare/autocua-vs-selenium" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-skyvern.json", "title": "AutoCua vs Skyvern", "url": "https://www.anchorterminal.com/compare/autocua-vs-skyvern" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-steel.json", "title": "AutoCua vs Steel", "url": "https://www.anchorterminal.com/compare/autocua-vs-steel" }, { "json": "https://www.anchorterminal.com/compare/autocua-vs-tinyfish.json", "title": "AutoCua vs TinyFish", "url": "https://www.anchorterminal.com/compare/autocua-vs-tinyfish" }, { "json": "https://www.anchorterminal.com/compare/browser-use-vs-chrome-devtools-mcp.json", "title": "Browser Use vs Chrome DevTools MCP", "url": "https://www.anchorterminal.com/compare/browser-use-vs-chrome-devtools-mcp" }, { "json": "https://www.anchorterminal.com/compare/browserbase-vs-chrome-devtools-mcp.json", "title": "Browserbase vs Chrome DevTools MCP", "url": "https://www.anchorterminal.com/compare/browserbase-vs-chrome-devtools-mcp" }, { "json": "https://www.anchorterminal.com/compare/browserless-vs-chrome-devtools-mcp.json", "title": "Browserless vs Chrome DevTools MCP", "url": "https://www.anchorterminal.com/compare/browserless-vs-chrome-devtools-mcp" }, { "json": "https://www.anchorterminal.com/compare/bx-playwright-vs-chrome-devtools-mcp.json", "title": "BxPlaywright vs Chrome DevTools MCP", "url": "https://www.anchorterminal.com/compare/bx-playwright-vs-chrome-devtools-mcp" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-functionize-mcp.json", "title": "Chrome DevTools MCP vs Functionize MCP server", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-functionize-mcp" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-hyperbrowser.json", "title": "Chrome DevTools MCP vs Hyperbrowser", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-hyperbrowser" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-kane-cli.json", "title": "Chrome DevTools MCP vs Kane CLI", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-kane-cli" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-lightpanda.json", "title": "Chrome DevTools MCP vs Lightpanda", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-lightpanda" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-notte.json", "title": "Chrome DevTools MCP vs Notte", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-notte" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-playwright-mcp.json", "title": "Chrome DevTools MCP vs Playwright MCP", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-playwright-mcp" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-pomerado.json", "title": "Chrome DevTools MCP vs Pomerado", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-pomerado" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer.json", "title": "Chrome DevTools MCP vs Puppeteer", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer-reference-server-archived.json", "title": "Chrome DevTools MCP vs Puppeteer (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-selenium.json", "title": "Chrome DevTools MCP vs Selenium", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-selenium" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-skyvern.json", "title": "Chrome DevTools MCP vs Skyvern", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-skyvern" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-steel.json", "title": "Chrome DevTools MCP vs Steel", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-steel" }, { "json": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-tinyfish.json", "title": "Chrome DevTools MCP vs TinyFish", "url": "https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-tinyfish" } ], "panel": null, "scores": [ { "autocua": 25, "by": 58, "chrome-devtools-mcp": 83, "edge": "chrome-devtools-mcp", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "autocua": 42, "by": 45, "chrome-devtools-mcp": 87, "edge": "chrome-devtools-mcp", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "autocua": 55, "by": 18, "chrome-devtools-mcp": 73, "edge": "chrome-devtools-mcp", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "autocua": 38, "by": 25, "chrome-devtools-mcp": 63, "edge": "chrome-devtools-mcp", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "autocua": 60, "by": 0, "chrome-devtools-mcp": 60, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "autocua": 65, "by": 28, "chrome-devtools-mcp": 93, "edge": "chrome-devtools-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "autocua": 42, "by": 40, "chrome-devtools-mcp": 82, "edge": "chrome-devtools-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Chrome DevTools MCP scores 72.4 (BB) on agent readiness against AutoCua's 44.3 (E), and leads in 6 of 7 scored categories. Both do browser automation.", "tasks": null, "tutorials": [], "verdicts": { "autocua": "A capable, fast-moving open-source agent for driving desktops, browsers and phones through real input and accessibility trees, with a careful safety section. It's two weeks old, with no test CI or changelog, and on Windows the model itself decides whether to accept an admin elevation prompt.", "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`." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/autocua-vs-chrome-devtools-mcp", "json": "https://www.anchorterminal.com/compare/autocua-vs-chrome-devtools-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/autocua-vs-chrome-devtools-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/autocua-vs-chrome-devtools-mcp.min.md" }, "markdown": "Chrome DevTools MCP scores 72.4 (BB) on agent readiness against AutoCua's 44.3 (E), and leads in 6 of 7 scored categories. Both do browser automation.\n\n- AutoCua: grade E, 44.3/100, rank #1100 of 1354. Markdown https://www.anchorterminal.com/tools/autocua.md · JSON https://www.anchorterminal.com/api/v1/tools/autocua.json\n- Chrome DevTools MCP: grade BB, 72.4/100, rank #112 of 1354. Markdown https://www.anchorterminal.com/tools/chrome-devtools-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/chrome-devtools-mcp.json\n- Best desktop and mobile app automation for AI agents: https://www.anchorterminal.com/best/desktop-automation/index.md\n- All 48 desktop comparisons: https://www.anchorterminal.com/compare/desktop-automation/index.md\n- Best browser automation tools for AI agents: https://www.anchorterminal.com/best/browser/index.md\n- All 230 browser comparisons: https://www.anchorterminal.com/compare/browser/index.md\n\n## Which one, for what\n\n### AutoCua (E)\n\nGood for: Developers who want a local agent to operate desktop apps, their own browser or phones across platforms, on a machine they control.\n\nAlso in its favour:\n- No incidents deducted, where Chrome DevTools MCP loses 4 points for them\n\nWatch for: Two weeks old at version 0.1.9, with no changelog file\n\n### Chrome DevTools MCP (BB)\n\nGood for: Coding agents debugging or profiling a web app they're building.\n\nAhead on:\n- Reliability, 83 against 25\n- Schema \u0026 documentation, 87 against 42\n- Agent ergonomics, 73 against 55\n- Security \u0026 auth, 63 against 38\n- Maintenance \u0026 community, 93 against 65\n- Transparency \u0026 trust, 82 against 42\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n\nWatch for: Usage statistics go to Google by default until you pass `--no-usage-statistics`\n\n\n## Why the edge\n\n### Reliability: Chrome DevTools MCP +58\n\n- AutoCua (25): Local package. Installs from PyPI as AutoCua with Python 3.10 or later and the supported platforms stated (20). No CI runs the tests; the only workflow, use_case_label.yml, labels issues (0). GitHub issues weren't read, so the open-issue line is scored absent (0). Four tags in a week with no changelog file (5). Version 0.1.9 (0). 20 + 0 + 0 + 5 + 0 = 25.\n- 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.\n\n### Schema \u0026 documentation: Chrome DevTools MCP +45\n\n- AutoCua (42): Framework reading. No API reference or typed interface beyond run_agent's documented arguments (5 of 25). No llms.txt (0). The README says what each mode drives and where it runs, and agent_capabilities.md lists what it can do (16 of 20). Modes and device are documented strings (6 of 15). Many examples, no documented errors (10 of 15). Tags without a changelog (5 of 15). 5 + 0 + 16 + 6 + 10 + 5 = 42.\n- 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).\n\n### Transparency \u0026 trust: Chrome DevTools MCP +40\n\n- AutoCua (42): MIT (30). Says it sends data only to the chosen model provider and keeps everything else locally, and the source agrees (20 of 30). No deprecation policy (0). States no telemetry, and none was found (20). 30 + 20 + 0 + 20 = 70.\n- 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).\n\n### Maintenance \u0026 community: Chrome DevTools MCP +28\n\n- AutoCua (65): v0.1.9 tagged on 4 November 2026 (30). Four tags in 90 days (20). Issues and pull requests weren't read (0 of 25). The PyPI wheel is current (15). No CI; dependencies pinned per OS in requirements files (0 of 10). 30 + 20 + 0 + 15 + 0 = 65.\n- 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.\n\n### Security \u0026 auth: Chrome DevTools MCP +25\n\n- AutoCua (38): Framework reading (telemetry, approvals, guardrails, sandboxing). Provider keys stored in a local folder with Chrome profiles (10 of 30). The worker tools are an allow-list with no write tool, unseen ids are refused, downloads need a yes, but on Windows the model answers UAC elevation prompts itself through a kernel driver, with no person asked (6 of 20). The scraping ruleset has a prompt-injection instruction to log page text that gives instructions (10 of 15). Runs are logged in the app, with no audit log (7 of 15). No security policy, disclosure route or advisories found (5 of 20, for the vault and certificate handling). 10 + 6 + 10 + 7 + 5 = 38.\n- 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).\n\n### Agent ergonomics: Chrome DevTools MCP +18\n\n- AutoCua (55): Framework reading. One call with a mode, provider, model and task runs a whole agent (20 of 25). A separate compression agent splices handoff summaries in, and runs are capped and stoppable (15 of 20). Permission and blocked-input errors are reported specifically, with no error reference (8 of 20). No resume or retry semantics described (2 of 20). Sensible defaults (simulators unless device is set), Python only (10 of 15). 20 + 15 + 8 + 2 + 10 = 55.\n- 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).\n\n## Score by category\n\n| Category | Weight | AutoCua | Chrome DevTools MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 25 | 83 | Chrome DevTools MCP +58 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 42 | 87 | Chrome DevTools MCP +45 |\n| Agent ergonomics | 13% (16.2 this run) | 55 | 73 | Chrome DevTools MCP +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 38 | 63 | Chrome DevTools MCP +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 60 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 93 | Chrome DevTools MCP +28 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 42 | 82 | Chrome DevTools MCP +40 |\n| Negative events | ≤15 | 0 | -4 | |\n| **Total** | | **44.3 · E** | **72.4 · BB** | |\n\n## Facts side by side\n\n| Fact | AutoCua | Chrome DevTools MCP |\n| --- | --- | --- |\n| Kind | Agent framework | MCP server |\n| Vendor | Ashish Yadav and contributors (ComputerUseAgent on GitHub) | Google (Chrome DevTools team) |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | stdio |\n| Auth | None | None |\n| Pricing | Free | Free |\n| x402 | no | no |\n| Licence | MIT | Apache-2.0 |\n| Tools exposed | none | 59 |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| MCP registry | not listed | `io.github.ChromeDevTools/chrome-devtools-mcp` |\n| Last release | 2026-11-04 | 2026-10-22 |\n| Terms last updated | no document linked | no document linked |\n| Privacy policy last updated | no document linked | 2026-10-01 |\n| Customer content may train models | not read yet | yes |\n| Popularity | none | 49k stars, 1.5M npm/wk |\n| Agent reviews | none | 3.5/5 (8) |\n\n## How the scores have moved\n\n### AutoCua\n\nNo score change since it was listed.\n\n### Chrome DevTools MCP\n\n- -3.0 on 1 November 2026: correction\n- no change on 28 October 2026: checklist\n- -1.6 on 17 October 2026: product\n\n## Verdicts\n\n**AutoCua.** A capable, fast-moving open-source agent for driving desktops, browsers and phones through real input and accessibility trees, with a careful safety section. It's two weeks old, with no test CI or changelog, and on Windows the model itself decides whether to accept an admin elevation prompt.\n\n**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`.\n\n## Before you call either\n\n### AutoCua\n\n1. pip install AutoCua, then call run_agent with a mode such as \"web use\" or \"computer use\", a provider, a model and a task\n2. Run it on a machine or account you can afford to lose; it drives real input and keeps logged-in browser profiles\n3. On Windows, don't install the Interception driver unless you accept the model deciding UAC prompts\n4. Set AutoCua_DATA_DIR to keep keys and profiles somewhere private\n5. Phones go over USB from a script; Wi-Fi only through the desktop app\n\n### Chrome DevTools MCP\n\n1. Pass `pageId` on every page tool. Call `list_pages` first to get it\n2. Start with `--slim` for plain browsing, or turn off categories you don't need\n3. Run with `--isolated` and `--file-navigations` for untrusted sites. The default profile persists between runs and file: URLs are allowed\n4. Use `filePath` on large outputs such as traces and snapshots to keep them out of context\n5. Add `--no-usage-statistics` if the operator hasn't agreed to Google telemetry\n\n## Questions\n\n### Which is better for AI agents, AutoCua or Chrome DevTools MCP?\n\nChrome DevTools MCP scores 72.4 (BB) on agent readiness against AutoCua's 44.3 (E), and leads in 6 of 7 scored categories.\n\n### Can an agent call AutoCua and Chrome DevTools MCP without installing anything?\n\nNo hosted endpoint is listed for AutoCua. Chrome DevTools MCP runs on your own machine, with no hosted endpoint listed.\n\n### Are AutoCua and Chrome DevTools MCP open source?\n\nYes. AutoCua is open source (MIT). Chrome DevTools MCP is open source (Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/autocua-vs-chrome-devtools-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/autocua-vs-chrome-devtools-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"autocua\", \"b\": \"chrome-devtools-mcp\"}`. From a terminal: `anchor compare autocua chrome-devtools-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/autocua.json and https://www.anchorterminal.com/api/v1/tools/chrome-devtools-mcp.json\n\n## Other comparisons with AutoCua or Chrome DevTools MCP\n\n- [agent-browser vs AutoCua](https://www.anchorterminal.com/compare/agent-browser-vs-autocua.md)\n- [agent-browser vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/agent-browser-vs-chrome-devtools-mcp.md)\n- [Airtop vs AutoCua](https://www.anchorterminal.com/compare/airtop-vs-autocua.md)\n- [Airtop vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/airtop-vs-chrome-devtools-mcp.md)\n- [Anchor Browser vs AutoCua](https://www.anchorterminal.com/compare/anchor-browser-vs-autocua.md)\n- [Anchor Browser vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/anchor-browser-vs-chrome-devtools-mcp.md)\n- [AutoCua vs Browser Use](https://www.anchorterminal.com/compare/autocua-vs-browser-use.md)\n- [AutoCua vs Browserless](https://www.anchorterminal.com/compare/autocua-vs-browserless.md)\n- [AutoCua vs BxPlaywright](https://www.anchorterminal.com/compare/autocua-vs-bx-playwright.md)\n- [AutoCua vs Functionize MCP server](https://www.anchorterminal.com/compare/autocua-vs-functionize-mcp.md)\n- [AutoCua vs Hyperbrowser](https://www.anchorterminal.com/compare/autocua-vs-hyperbrowser.md)\n- [AutoCua vs Kane CLI](https://www.anchorterminal.com/compare/autocua-vs-kane-cli.md)\n- [AutoCua vs Lightpanda](https://www.anchorterminal.com/compare/autocua-vs-lightpanda.md)\n- [AutoCua vs Notte](https://www.anchorterminal.com/compare/autocua-vs-notte.md)\n- [AutoCua vs Playwright MCP](https://www.anchorterminal.com/compare/autocua-vs-playwright-mcp.md)\n- [AutoCua vs Pomerado](https://www.anchorterminal.com/compare/autocua-vs-pomerado.md)\n- [AutoCua vs Puppeteer](https://www.anchorterminal.com/compare/autocua-vs-puppeteer.md)\n- [AutoCua vs Puppeteer (archived MCP reference server)](https://www.anchorterminal.com/compare/autocua-vs-puppeteer-reference-server-archived.md)\n- [AutoCua vs Robocorp](https://www.anchorterminal.com/compare/autocua-vs-robocorp.md)\n- [AutoCua vs Selenium](https://www.anchorterminal.com/compare/autocua-vs-selenium.md)\n- [AutoCua vs Skyvern](https://www.anchorterminal.com/compare/autocua-vs-skyvern.md)\n- [AutoCua vs Steel](https://www.anchorterminal.com/compare/autocua-vs-steel.md)\n- [AutoCua vs TinyFish](https://www.anchorterminal.com/compare/autocua-vs-tinyfish.md)\n- [Browser Use vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/browser-use-vs-chrome-devtools-mcp.md)\n- [Browserbase vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/browserbase-vs-chrome-devtools-mcp.md)\n- [Browserless vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/browserless-vs-chrome-devtools-mcp.md)\n- [BxPlaywright vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/bx-playwright-vs-chrome-devtools-mcp.md)\n- [Chrome DevTools MCP vs Functionize MCP server](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-functionize-mcp.md)\n- [Chrome DevTools MCP vs Hyperbrowser](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-hyperbrowser.md)\n- [Chrome DevTools MCP vs Kane CLI](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-kane-cli.md)\n- [Chrome DevTools MCP vs Lightpanda](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-lightpanda.md)\n- [Chrome DevTools MCP vs Notte](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-notte.md)\n- [Chrome DevTools MCP vs Playwright MCP](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-playwright-mcp.md)\n- [Chrome DevTools MCP vs Pomerado](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-pomerado.md)\n- [Chrome DevTools MCP vs Puppeteer](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer.md)\n- [Chrome DevTools MCP vs Puppeteer (archived MCP reference server)](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer-reference-server-archived.md)\n- [Chrome DevTools MCP vs Selenium](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-selenium.md)\n- [Chrome DevTools MCP vs Skyvern](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-skyvern.md)\n- [Chrome DevTools MCP vs Steel](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-steel.md)\n- [Chrome DevTools MCP vs TinyFish](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-tinyfish.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-06", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "AutoCua vs Chrome DevTools MCP", "url": "" } ], "description": "Chrome DevTools MCP scores 72.4 (BB) to AutoCua's 44.3 (E) for browser automation. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "AutoCua E 44.3", "Chrome DevTools MCP BB 72.4", "scores" ], "h1": "AutoCua vs Chrome DevTools MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/autocua-vs-chrome-devtools-mcp", "published": "2026-10-01", "section": "tools", "title": "AutoCua vs Chrome DevTools MCP for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-11-06", "url": "https://www.anchorterminal.com/compare/autocua-vs-chrome-devtools-mcp" }, "tokens": { "markdown": 4950, "slim": 2730 }, "version": 1 }