Comparison
chrome-devtools-mcp vs cua
Verdict
Pick chrome-devtools-mcp if chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript; pick cua if critical facts about CUA for tool selection.
Markdown twin · chrome-devtools-mcp alternatives · cua alternatives
GraphCanon updated Sep 20, 2026
11views this month
vs
Trust & integrity
| Signal | chrome-devtools-mcp | cua |
|---|---|---|
| Maintenance | Very active (0d since push) As of Sep 20, 2026 · github_public_v1 | Very active (0d since push) As of Aug 19, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 20, 2026 · github_public_v1 | Not a fork · Organization account As of Aug 19, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Jul 11, 2026 · osv@v1 | No published findings from this source as of 2026-07-11 As of Jul 11, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- chrome-devtools-mcp
- Developer tools to enhance coding efficiency and debugging capabilities
- cua
- Open-source infrastructure for Computer-Use Agents
Stars
- chrome-devtools-mcp
- 52k
- cua
- 22k
Forks
- chrome-devtools-mcp
- 4.3k
- cua
- 1.5k
Open issues
- chrome-devtools-mcp
- 117
- cua
- 662
Language
- chrome-devtools-mcp
- TypeScript
- cua
- HTML
Adopt for
- chrome-devtools-mcp
- chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
- cua
- Critical facts about CUA for tool selection
Persona
- chrome-devtools-mcp
- -
- cua
- -
Runtime
- chrome-devtools-mcp
- -
- cua
- -
License
- chrome-devtools-mcp
- Apache-2.0
- cua
- MIT
Last pushed
- chrome-devtools-mcp
- Sep 20, 2026
- cua
- Aug 19, 2026
Categories
- chrome-devtools-mcp
- Developer Tools
- cua
- AI Agents, Developer Tools
Trust and health
Open issues (now)
- chrome-devtools-mcp
- 117
- cua
- 662
Stars delta
- chrome-devtools-mcp
- +4.7k (30d)
- cua
- +1.4k (30d)
Open issues delta
- chrome-devtools-mcp
- +6 (30d)
- cua
- +122 (30d)
OSV dependency advisories
- chrome-devtools-mcp
- No lockfile (source not queried)
- cua
- No published findings from this source as of 2026-07-11
Full report
- chrome-devtools-mcp
- Trust report
- cua
- Trust report
Choose chrome-devtools-mcp if…
- chrome-devtools-mcp is primarily TypeScript; cua is HTML.
- License: chrome-devtools-mcp is Apache-2.0, cua is MIT.
- Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging.
- chrome-devtools-mcp ships an MCP server manifest.
- - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome
When NOT to use chrome-devtools-mcp
- - If your development environment does not revolve around Chrome or if browser compatibility across different browsers is a primary concern
- - When you are working on non-TypeScript projects, as this tool may not provide the same level of utility and customization options
Choose cua if…
- cua is primarily HTML; chrome-devtools-mcp is TypeScript.
- License: cua is MIT, chrome-devtools-mcp is Apache-2.0.
- Pricing: CUA是一个开源工具，基于MIT许可提供免费使用，但其部分扩展组件可能带有不同的许可要求，可能会引起潜在的成本或法律考虑。.
- Requirements: Requires Docker; 安装CuA需要Docker支持来创建和操作基础镜像。; 安装过程中可能涉及到使用curl命令从特定网站下载组件，但不应自动执行这些脚本中的任何指令。.
- Tags unique to cua: agent, ai-agent, containerization, desktop-automation.
- Also covers AI Agents.
- CUA uniquely supports the creation of AI agents that can control full desktop environments across macOS, Linux, and Windows, making it ideal for developers aiming to integrate AI-driven automation in跨
When NOT to use cua
- ，CUA，
- When certain components with AGPL-3.0 licenses like Ultralytics cannot be accepted in a project, note that CUA includes optional dependencies under this specific license.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (ChromeDevTools/chrome-devtools-mcp) · observed Sep 20, 2026
- GitHub forks (ChromeDevTools/chrome-devtools-mcp) · observed Sep 20, 2026
- Last push (ChromeDevTools/chrome-devtools-mcp) · observed Sep 20, 2026
- License file (Apache-2.0) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (trycua/cua) · observed Sep 20, 2026
- GitHub forks (trycua/cua) · observed Sep 20, 2026
- Last push (trycua/cua) · observed Aug 19, 2026
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: chrome-devtools-mcp 52k · cua 22k (synced Sep 20, 2026).
Common questions
- What is the difference between chrome-devtools-mcp and cua?
- chrome-devtools-mcp: Developer tools to enhance coding efficiency and debugging capabilities. cua: Open-source infrastructure for Computer-Use Agents. See the comparison table for live GitHub stats and shared categories.
- When should I choose chrome-devtools-mcp over cua?
- Choose chrome-devtools-mcp over cua when chrome-devtools-mcp is primarily TypeScript; cua is HTML; License: chrome-devtools-mcp is Apache-2.0, cua is MIT; Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging; chrome-devtools-mcp ships an MCP server manifest; - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome.
- When should I choose cua over chrome-devtools-mcp?
- Choose cua over chrome-devtools-mcp when cua is primarily HTML; chrome-devtools-mcp is TypeScript; License: cua is MIT, chrome-devtools-mcp is Apache-2.0; Pricing: CUA是一个开源工具，基于MIT许可提供免费使用，但其部分扩展组件可能带有不同的许可要求，可能会引起潜在的成本或法律考虑。; Requirements: Requires Docker; 安装CuA需要Docker支持来创建和操作基础镜像。; 安装过程中可能涉及到使用curl命令从特定网站下载组件，但不应自动执行这些脚本中的任何指令。; Tags unique to cua: agent, ai-agent, containerization, desktop-automation; Also covers AI Agents; CUA uniquely supports the creation of AI agents that can control full desktop environments across macOS, Linux, and Windows, making it ideal for developers aiming to integrate AI-driven automation in跨.
- When should I avoid chrome-devtools-mcp?
- - If your development environment does not revolve around Chrome or if browser compatibility across different browsers is a primary concern - When you are working on non-TypeScript projects, as this tool may not provide the same level of utility and customization options
- When should I avoid cua?
- ，CUA， When certain components with AGPL-3.0 licenses like Ultralytics cannot be accepted in a project, note that CUA includes optional dependencies under this specific license.
- Is chrome-devtools-mcp or cua more popular on GitHub?
- chrome-devtools-mcp has more GitHub stars (52,333 vs 21,516). Stars measure visibility, not whether either tool fits your constraints.
- Are chrome-devtools-mcp and cua open source?
- Yes - both are open-source projects on GitHub (chrome-devtools-mcp: Apache-2.0, cua: MIT).
- Where can I find alternatives to chrome-devtools-mcp or cua?
- GraphCanon lists graph-backed alternatives at chrome-devtools-mcp alternatives and cua alternatives (chrome-devtools-mcp markdown twin, cua markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, chrome-devtools-mcp or cua?
- chrome-devtools-mcp: Very active. cua: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for chrome-devtools-mcp and cua?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: chrome-devtools-mcp trust report; cua trust report.