head to head · open source
chrome-devtools-mcp vs ublacklist
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. ublacklist has 6,674 stars, 349 forks, 2 open issues and last shipped 3 days ago. chrome-devtools-mcp leads on adoption by 719% (54,665 vs 6,674 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; ublacklist is written in TypeScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, ublacklist 5%. 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 | ublacklist | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 6.7K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-10-31 |
| Forks | ⑂ 5.3K | ⑂ 349 |
| 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 ublacklist if
- You want the ublacklist feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and ublacklist 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 ublacklist
uBlacklist English Deutsch 简体中文 Blocks specific sites from appearing in Google search results Chrome : Chrome Web Store Firefox : Firefox Add ons Edge : Edge Add ons Safari : App Store (macOS and iOS, thanks to Group Leafy) Description This extension prevents the sites you specify from appearing in Google search results. You can add rules on search result pages, or on sites to be blocked by clicking the toolbar icon. Rules can be specified either by match patterns (e.g. :// .example.com/ ) or by expressions including regular expressions, variables and string matchers (e.g. /example\.(net org)/ , path ="example"i…
read the full ublacklist 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 ublacklist more popular?
chrome-devtools-mcp has 54,665 GitHub stars and ublacklist has 6,674. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and ublacklist free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and ublacklist under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and ublacklist?
chrome-devtools-mcp is written in TypeScript and ublacklist 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 ublacklist?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose ublacklist if its feature set, stack or MIT licence fits better. Both are self-hostable.