head to head · open source

chrome-devtools-mcp vs browserify

chrome-devtools-mcp has 52,276 GitHub stars, 4,131 forks, 109 open issues and last shipped yesterday. browserify has 14,695 stars, 1,202 forks, 387 open issues and last shipped yesterday. chrome-devtools-mcp leads on adoption by 256% (52,276 vs 14,695 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; browserify is written in JavaScript under MIT. chrome-devtools-mcp has attracted 8% as many forks as stars, browserify 8%. browserify 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.

chrome-devtools-mcp ★ 52K browserify ★ 15K category Productivity & Utilities

← all 15422 open source comparisons

Side by side

chrome-devtools-mcp browserify
GitHub stars ★ 52K ★ 15K
License Apache-2.0 MIT
Written in TypeScript JavaScript
Last push 2026-09-18 2026-09-18
Forks ⑂ 4.1K ⑂ 1.2K
Self-hosting Yes Yes
Data ownership Your server Your server

pick chrome-devtools-mcp if

  • You weight community size — 52K 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

full chrome-devtools-mcp profile →

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

full browserify profile →

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 →

About browserify

Browserify is an MIT licensed JavaScript command line bundler, installed from npm, that lets browser code use Node style require() calls and bundles the whole dependency graph into a single script you serve with a tag.

read the full browserify overview →

More in Productivity & Utilities

n8n ★ 205K Excalidraw ★ 132K RustDesk ★ 124K Browser Use ★ 115K LocalSend ★ 92K AppFlowy ★ 77K

Related comparisons

browser-use vs chrome-devtools-mcp ublock vs chrome-devtools-mcp ladybird vs chrome-devtools-mcp ublock vs ladybird ublock vs monaco-editor ladybird vs monaco-editor ublock vs zen-browser ladybird vs zen-browser openclaw vs khoj open-webui vs open-notebook open-webui vs khoj appflowy vs affine appflowy vs memos appflowy vs plane appflowy vs joplin mem0 vs memos n8n vs langchain n8n vs browser-use firecrawl vs browser-use n8n vs langgraph n8n vs frigate n8n vs lightpanda n8n vs proxmoxve n8n vs activepieces

More Browsers & Extensions projects

Compare either of these against the rest of the Browsers & Extensions field.

chrome-devtools-mcp vs uBlock chrome-devtools-mcp vs Ladybird chrome-devtools-mcp vs monaco-editor chrome-devtools-mcp vs Zen Browser chrome-devtools-mcp vs servo chrome-devtools-mcp vs serenity chrome-devtools-mcp vs refined-github chrome-devtools-mcp vs slate chrome-devtools-mcp vs Avalonia chrome-devtools-mcp vs webtorrent chrome-devtools-mcp vs fingerprintjs chrome-devtools-mcp vs obscura

Frequently asked questions

Is chrome-devtools-mcp or browserify more popular?

chrome-devtools-mcp has 52,276 GitHub stars and browserify has 14,695. 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 (52,276 stars) or its Apache-2.0 licence terms. Choose browserify if its feature set, stack or MIT licence fits better. Both are self-hostable.