head to head · open source
chrome-devtools-mcp vs keepassxc-browser
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. keepassxc-browser has 2,382 stars, 257 forks, 197 open issues and last shipped 6 days ago. chrome-devtools-mcp leads on adoption by 2,195% (54,665 vs 2,382 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; keepassxc-browser is written in JavaScript under GPL-3.0. chrome-devtools-mcp has attracted 10% as many forks as stars, keepassxc-browser 11%. 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 | keepassxc-browser | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 2.4K |
| License | Apache-2.0 | GPL-3.0 |
| Written in | TypeScript | JavaScript |
| Last push | 2026-11-02 | 2026-10-28 |
| Forks | ⑂ 5.3K | ⑂ 257 |
| 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 keepassxc-browser if
- You want the keepassxc-browser feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches JavaScript
- You evaluated both and keepassxc-browser 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 keepassxc-browser
KeePassXC Browser Browser extension for KeePassXC with native messaging. Download and use This browser extension was first supported in KeePassXC 2.3.0 (release end of 2017). In general it is advised to only use the latest available release. Get the extension for Firefox or Chrome/Chromium or Microsoft Edge. Please see this document for instructions how to configure KeePassXC in order to connect the database correctly. How it works KeePassXC Browser communicates with KeePassXC through keepassxc proxy . The proxy handles listening to STDIN/STDOUT and transfers these messages through Unix domain sockets / named…
read the full keepassxc-browser 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 keepassxc-browser more popular?
chrome-devtools-mcp has 54,665 GitHub stars and keepassxc-browser has 2,382. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and keepassxc-browser free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and keepassxc-browser under GPL-3.0. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and keepassxc-browser?
chrome-devtools-mcp is written in TypeScript and keepassxc-browser 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 keepassxc-browser?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose keepassxc-browser if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.