head to head · open source
uBlock vs chrome-devtools-mcp
uBlock has 69,033 GitHub stars, 4,427 forks, 15 open issues and last shipped yesterday. chrome-devtools-mcp has 54,665 stars, 5,250 forks, 109 open issues and last shipped yesterday. uBlock leads on adoption by 26% (69,033 vs 54,665 stars). uBlock is written in JavaScript under GPL-3.0; chrome-devtools-mcp is written in TypeScript under Apache-2.0. uBlock has attracted 6% as many forks as stars, chrome-devtools-mcp 10%. uBlock 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
| uBlock | chrome-devtools-mcp | |
|---|---|---|
| GitHub stars | ★ 69K | ★ 55K |
| License | GPL-3.0 | Apache-2.0 |
| Written in | JavaScript | TypeScript |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 4.4K | ⑂ 5.3K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick uBlock if
- You weight community size — 69K stars and counting
- You want the GPL-3.0 license terms
- Your stack matches JavaScript
- 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 uBlock
[![Badge Commits]][Commit Rate] [![Badge Issues]][Issues] [![Badge Localization]][Crowdin] [![Badge License]][License] [![Badge NPM]][NPM] [![Badge Mozilla]][Mozilla] ![Badge Chrome] [![Badge Edge]][Edge] uBlock Origin (uBO) GitHub Releases Stable and development versions on Firefox, Chromium MV2, and Thunderbird. Must be placed manually into web browsers; the Chromium and Thunderbird versions usually won't auto update. Related: uBlock Origin Lite uBlock Origin (uBO) is a CPU and memory efficient [wide spectrum content blocker][Blocking] for Chromium and Firefox. It blocks ads, trackers, coin miners, popups…
read the full uBlock overview →
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 →
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 uBlock or chrome-devtools-mcp more popular?
uBlock has 69,033 GitHub stars and chrome-devtools-mcp has 54,665. uBlock has the larger community by that measure.
Are uBlock and chrome-devtools-mcp free?
Both are open source. uBlock is licensed under GPL-3.0 and chrome-devtools-mcp under Apache-2.0. Neither carries a licence fee.
What is the difference between uBlock and chrome-devtools-mcp?
uBlock is written in JavaScript 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, uBlock or chrome-devtools-mcp?
Choose uBlock if you want the larger community (69,033 stars) or its GPL-3.0 licence terms. Choose chrome-devtools-mcp if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.