head to head · open source
chrome-devtools-mcp vs Browser Operator
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. Browser Operator has 516 stars, 83 forks, 15 open issues and last shipped 8 months ago. chrome-devtools-mcp leads on adoption by 10,494% (54,665 vs 516 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; Browser Operator is written in TypeScript under BSD-3-Clause. chrome-devtools-mcp has attracted 10% as many forks as stars, Browser Operator 16%. 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 20902 open source comparisons
Side by side
| chrome-devtools-mcp | Browser Operator | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 516 |
| License | Apache-2.0 | BSD-3-Clause |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-03-19 |
| Forks | ⑂ 5.3K | ⑂ 83 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick chrome-devtools-mcp if
- You weight community size — 55K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick Browser Operator if
- You want the Browser Operator feature set and don't need the biggest community
- You prefer the BSD-3-Clause license terms
- Your stack matches TypeScript
- You evaluated both and Browser Operator fits your workflow better
About chrome-devtools-mcp
Chrome DevTools for agents Chrome DevTools for agents ( chrome devtools mcp ) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It acts as a Model Context Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in depth debugging, and performance analysis. A [CLI][cli] is also provided for use without MCP. [Tool reference][tool reference] [Changelog][changelog] [Contributing][contributing] [Troubleshooting][troubleshooting] [Design Principles][design principles] Key features Get…
read the full chrome-devtools-mcp overview →
About Browser Operator
Open source, privacy focused AI browser that transforms how you work on the web. An intelligent platform for research, analysis, and automation—running locally in your browser. Download • Docs • Community 🚀 Getting Started ⬇️ Download for macOS ⬇️ Download for Windows System Requirements: macOS 10.15+ or Windows 10 (64 bit)+ • 8GB RAM (16GB recommended) • 2GB free disk space AI Provider Setup Quick Setup: Settings → Select provider → Enter credentials → Choose model → Save 🎬 What You Can Do Multi Agent Automation – Specialized AI agents work together to handle complex web tasks autonomously Privacy First – All…
read the full Browser Operator overview →
More in Productivity & Utilities
Related comparisons
More Browsers & Extensions projects
Compare either of these against the rest of the Browsers & Extensions field.
Frequently asked questions
Is chrome-devtools-mcp or Browser Operator more popular?
chrome-devtools-mcp has 54,665 GitHub stars and Browser Operator has 516. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and Browser Operator free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and Browser Operator under BSD-3-Clause. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and Browser Operator?
chrome-devtools-mcp is written in TypeScript and Browser Operator 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, chrome-devtools-mcp or Browser Operator?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose Browser Operator if its feature set, stack or BSD-3-Clause licence fits better. Both are self-hostable.