head to head · open source
chrome-devtools-mcp vs brownies
chrome-devtools-mcp has 54,053 GitHub stars, 6,496 forks, 109 open issues and last shipped 2 days ago. brownies has 2,564 stars, 61 forks, 0 open issues and last shipped yesterday. chrome-devtools-mcp leads on adoption by 2,008% (54,053 vs 2,564 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; brownies is written in TypeScript under MIT. chrome-devtools-mcp has attracted 12% as many forks as stars, brownies 2%. brownies was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (browser), so they are genuine substitutes rather than adjacent tools.
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 | brownies | |
|---|---|---|
| GitHub stars | ★ 54K | ★ 2.6K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-10-23 | 2026-10-24 |
| Forks | ⑂ 6.5K | ⑂ 61 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick chrome-devtools-mcp if
- You weight community size — 54K 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 brownies if
- You want the brownies feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and brownies 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 brownies
Brownies Tastier cookies , local , session , and db storage in a tiny package: Subscribe to changes in any of the objects: You can also iterate them as expected with Object.keys() , Object.values() , etc: Getting started Install it with npm: Then import the different parts: Or use a CDN for the browser: If you just want to play, go to the JSFiddle playground . Cookies Manipulate cookies with the simple getter/setter interface: Cookies will retain the types that is set. This is possible thanks to the underlying library: Warning: Manually setting cookies with document.cookie or server side [click for details]…
read the full brownies 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 brownies more popular?
chrome-devtools-mcp has 54,053 GitHub stars and brownies has 2,564. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and brownies free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and brownies under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and brownies?
chrome-devtools-mcp is written in TypeScript and brownies 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 brownies?
Choose chrome-devtools-mcp if you want the larger community (54,053 stars) or its Apache-2.0 licence terms. Choose brownies if its feature set, stack or MIT licence fits better. Both are self-hostable.