head to head · open source
chrome-devtools-mcp vs finicky
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. finicky has 5,241 stars, 227 forks, 53 open issues and last shipped 6 days ago. chrome-devtools-mcp leads on adoption by 943% (54,665 vs 5,241 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; finicky is written in Go under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, finicky 4%. 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 | finicky | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 5.2K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | Go |
| Last push | 2026-11-02 | 2026-10-28 |
| Forks | ⑂ 5.3K | ⑂ 227 |
| 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 finicky if
- You want the finicky feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and finicky 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 finicky
Always open the right browser Finicky is a macOS application that allows you to set up rules that decide which browser is opened for every url. With Finicky as your default browser, you can tell it to open Bluesky or Reddit in one browser, and LinkedIn or Google Meet in another. Route any URL to your preferred browser with powerful matching rules Automatically edit URLs before opening them (e.g., force HTTPS, remove tracking parameters) Write rules in JavaScript or TypeScript for complete control Create complex routing logic with regular expressions and custom functions Handle multiple browsers and apps with a…
read the full finicky 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 finicky more popular?
chrome-devtools-mcp has 54,665 GitHub stars and finicky has 5,241. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and finicky free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and finicky under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and finicky?
chrome-devtools-mcp is written in TypeScript and finicky in Go. 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 finicky?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose finicky if its feature set, stack or MIT licence fits better. Both are self-hostable.