Comparison
browser-use vs chrome-devtools-mcp
Verdict
Pick browser-use if browser-use is a Python-based repository for AI agents designed for browser automation using Playwright; pick chrome-devtools-mcp if chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
Markdown twin · browser-use alternatives · chrome-devtools-mcp alternatives
GraphCanon updated Sep 20, 2026
8views this month
vs
Trust & integrity
| Signal | browser-use | chrome-devtools-mcp |
|---|---|---|
| Maintenance | Very active (2d since push) As of Sep 18, 2026 · github_public_v1 | Very active (0d since push) As of Sep 20, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 18, 2026 · github_public_v1 | Not a fork · Organization account As of Sep 20, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Sep 18, 2026 · osv@v1 | No lockfile (source not queried) 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
- browser-use
- Agents that use the browser
- chrome-devtools-mcp
- Developer tools to enhance coding efficiency and debugging capabilities
Stars
- browser-use
- 115k
- chrome-devtools-mcp
- 52k
Forks
- browser-use
- 13k
- chrome-devtools-mcp
- 4.3k
Open issues
- browser-use
- 439
- chrome-devtools-mcp
- 117
Language
- browser-use
- Python
- chrome-devtools-mcp
- TypeScript
Adopt for
- browser-use
- browser-use is a Python-based repository for AI agents designed for browser automation using Playwright.
- chrome-devtools-mcp
- chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
Persona
- browser-use
- -
- chrome-devtools-mcp
- -
Runtime
- browser-use
- -
- chrome-devtools-mcp
- -
License
- browser-use
- MIT
- chrome-devtools-mcp
- Apache-2.0
Last pushed
- browser-use
- Sep 15, 2026
- chrome-devtools-mcp
- Sep 20, 2026
Categories
- browser-use
- AI Agents, Developer Tools
- chrome-devtools-mcp
- Developer Tools
Trust and health
Days since push
- browser-use
- 2d
- chrome-devtools-mcp
- 0d
Open issues (now)
- browser-use
- 439
- chrome-devtools-mcp
- 117
Stars delta
- browser-use
- +5.7k (30d)
- chrome-devtools-mcp
- +4.7k (30d)
Open issues delta
- browser-use
- +82 (30d)
- chrome-devtools-mcp
- +6 (30d)
Full report
- browser-use
- Trust report
- chrome-devtools-mcp
- Trust report
Choose browser-use if…
- browser-use is primarily Python; chrome-devtools-mcp is TypeScript.
- License: browser-use is MIT, chrome-devtools-mcp is Apache-2.0.
- Tags unique to browser-use: ai-agents, ai-tools, browser-automation, llm.
- Also covers AI Agents.
- browser-use ships Docker support for self-hosted deployment.
- When you need to automate browser actions with AI agents and prefer using Playwright for its robust capabilities in handling modern web applications.
When NOT to use browser-use
- If your project requires a different browser automation tool that is not Playwright, as browser-use is specifically tailored for Playwright integration.
- When detailed documentation and integrations provided by browser-use do not align with your project's specific needs or if you prefer a more generalized approach to browser automation.
Choose chrome-devtools-mcp if…
- chrome-devtools-mcp is primarily TypeScript; browser-use is Python.
- License: chrome-devtools-mcp is Apache-2.0, browser-use 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
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (browser-use/browser-use) · observed Sep 20, 2026
- GitHub forks (browser-use/browser-use) · observed Sep 20, 2026
- Last push (browser-use/browser-use) · observed Sep 15, 2026
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Sep 18, 2026
- Trust scan (lockfile / OSV) · observed Sep 18, 2026
- 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 on cards: browser-use 115k · chrome-devtools-mcp 52k (synced Sep 20, 2026).
Common questions
- What is the difference between browser-use and chrome-devtools-mcp?
- browser-use: Agents that use the browser. chrome-devtools-mcp: Developer tools to enhance coding efficiency and debugging capabilities. See the comparison table for live GitHub stats and shared categories.
- When should I choose browser-use over chrome-devtools-mcp?
- Choose browser-use over chrome-devtools-mcp when browser-use is primarily Python; chrome-devtools-mcp is TypeScript; License: browser-use is MIT, chrome-devtools-mcp is Apache-2.0; Tags unique to browser-use: ai-agents, ai-tools, browser-automation, llm; Also covers AI Agents; browser-use ships Docker support for self-hosted deployment; When you need to automate browser actions with AI agents and prefer using Playwright for its robust capabilities in handling modern web applications.
- When should I choose chrome-devtools-mcp over browser-use?
- Choose chrome-devtools-mcp over browser-use when chrome-devtools-mcp is primarily TypeScript; browser-use is Python; License: chrome-devtools-mcp is Apache-2.0, browser-use 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 avoid browser-use?
- If your project requires a different browser automation tool that is not Playwright, as browser-use is specifically tailored for Playwright integration. When detailed documentation and integrations provided by browser-use do not align with your project's specific needs or if you prefer a more generalized approach to browser automation.
- 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
- Is browser-use or chrome-devtools-mcp more popular on GitHub?
- browser-use has more GitHub stars (115,057 vs 52,333). Stars measure visibility, not whether either tool fits your constraints.
- Are browser-use and chrome-devtools-mcp open source?
- Yes - both are open-source projects on GitHub (browser-use: MIT, chrome-devtools-mcp: Apache-2.0).
- Where can I find alternatives to browser-use or chrome-devtools-mcp?
- GraphCanon lists graph-backed alternatives at browser-use alternatives and chrome-devtools-mcp alternatives (browser-use markdown twin, chrome-devtools-mcp 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, browser-use or chrome-devtools-mcp?
- browser-use: Very active. chrome-devtools-mcp: 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 browser-use and chrome-devtools-mcp?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: browser-use trust report; chrome-devtools-mcp trust report.