head to head · open source
Browser Use vs chrome-devtools-mcp
Browser Use has 115,022 GitHub stars, 12,661 forks, 421 open issues and last shipped 3 days ago. chrome-devtools-mcp has 52,222 stars, 4,037 forks, 109 open issues and last shipped today. Browser Use leads on adoption by 120% (115,022 vs 52,222 stars). Browser Use is written in Python under MIT; chrome-devtools-mcp is written in TypeScript under Apache-2.0. Browser Use has attracted 11% as many forks as stars, chrome-devtools-mcp 8%. chrome-devtools-mcp was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 13541 open source comparisons
Side by side
| Browser Use | chrome-devtools-mcp | |
|---|---|---|
| GitHub stars | ★ 115K | ★ 52K |
| License | MIT | Apache-2.0 |
| Written in | Python | TypeScript |
| Last push | 2026-09-15 | 2026-09-18 |
| Forks | ⑂ 13K | ⑂ 4.0K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Browser Use if
- You weight community size — 115K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick chrome-devtools-mcp if
- You want the chrome-devtools-mcp feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches TypeScript
- You evaluated both and chrome-devtools-mcp fits your workflow better
About Browser Use
Browser Use is an open source Python library and hosted platform that enables AI agents to control web browsers programmatically. It lives in the AI agent and browser automation ecosystem, built on Playwright and designed to let LLMs interact with websites as a human would—clicking, filling forms, solving CAPTCHAs, and navigating dynamic interfaces. The project provides three deployment paths: a fully hosted cloud service, a command line interface for existing agents, and a local Python library for custom integrations.
read the full Browser Use overview →
About chrome-devtools-mcp
chrome devtools mcp is an Apache 2.0 TypeScript Model Context Protocol server, distributed on npm, that gives coding agents such as Claude, Cursor, Copilot and Antigravity control over and visibility into a live Chrome browser through the full Chrome DevTools toolset.
read the full chrome-devtools-mcp overview →
More in Productivity & Utilities
Related comparisons
More Automation projects
Compare either of these against the rest of the Automation field.
Frequently asked questions
Is Browser Use or chrome-devtools-mcp more popular?
Browser Use has 115,022 GitHub stars and chrome-devtools-mcp has 52,222. Browser Use has the larger community by that measure.
Are Browser Use and chrome-devtools-mcp free?
Both are open source. Browser Use is licensed under MIT and chrome-devtools-mcp under Apache-2.0. Neither carries a licence fee.
What is the difference between Browser Use and chrome-devtools-mcp?
Browser Use is written in Python and chrome-devtools-mcp in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Browser Use or chrome-devtools-mcp?
Choose Browser Use if you want the larger community (115,022 stars) or its MIT licence terms. Choose chrome-devtools-mcp if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.