head to head · open source
chrome-devtools-mcp vs feathers
chrome-devtools-mcp has 54,631 GitHub stars, 5,246 forks, 109 open issues and last shipped 2 days ago. feathers has 15,257 stars, 802 forks, 121 open issues and last shipped 2 days ago. chrome-devtools-mcp leads on adoption by 258% (54,631 vs 15,257 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; feathers is written in TypeScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, feathers 5%. 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 | feathers | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 15K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-01 | 2026-11-01 |
| Forks | ⑂ 5.2K | ⑂ 802 |
| 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 feathers if
- You want the feathers feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and feathers 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 feathers
Feathers is a full stack framework for creating web APIs and real time applications with TypeScript or JavaScript. Feathers can interact with any backend technology, supports many databases out of the box and works with any frontend like React, VueJS, Angular, React Native, Android or iOS. Getting started Get started with just three commands: To learn more about Feathers visit the website at feathersjs.com or jump right into the Feathers guides. Contributing To start developing, clone this repository, then run: To run all tests run Individual tests can be run in the module you are working on: License Copyright…
read the full feathers 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 feathers more popular?
chrome-devtools-mcp has 54,631 GitHub stars and feathers has 15,257. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and feathers free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and feathers under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and feathers?
chrome-devtools-mcp is written in TypeScript and feathers 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 feathers?
Choose chrome-devtools-mcp if you want the larger community (54,631 stars) or its Apache-2.0 licence terms. Choose feathers if its feature set, stack or MIT licence fits better. Both are self-hostable.