head to head · open source
chrome-devtools-mcp vs browserify
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. browserify has 14,693 stars, 1,202 forks, 387 open issues and last shipped 10 days ago. chrome-devtools-mcp leads on adoption by 272% (54,665 vs 14,693 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; browserify is written in JavaScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, browserify 8%. chrome-devtools-mcp 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 | browserify | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 15K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | JavaScript |
| Last push | 2026-11-02 | 2026-10-24 |
| Forks | ⑂ 5.3K | ⑂ 1.2K |
| 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 browserify if
- You want the browserify feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches JavaScript
- You evaluated both and browserify 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 browserify
browserify require('modules') in the browser Use a node style require() to organize your browser code and load modules installed by npm. browserify will recursively analyze all the require() calls in your app in order to build a bundle you can serve up to the browser in a single into your html! install With npm do: usage compatibility Many npm modules that don't do IO will just work after being browserified. Others take more work. Many node built in modules have been wrapped to work in the browser, but only when you explicitly require() or use their functionality. When you require() any of these modules, you…
read the full browserify 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 browserify more popular?
chrome-devtools-mcp has 54,665 GitHub stars and browserify has 14,693. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and browserify free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and browserify under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and browserify?
chrome-devtools-mcp is written in TypeScript and browserify in JavaScript. 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 browserify?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose browserify if its feature set, stack or MIT licence fits better. Both are self-hostable.