head to head · open source
chrome-devtools-mcp vs keyFinder
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. keyFinder has 729 stars, 128 forks, 5 open issues and last shipped 10 days ago. chrome-devtools-mcp leads on adoption by 7,399% (54,665 vs 729 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; keyFinder is written in JavaScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, keyFinder 18%. 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 | keyFinder | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 729 |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | JavaScript |
| Last push | 2026-11-02 | 2026-10-24 |
| Forks | ⑂ 5.3K | ⑂ 128 |
| 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 keyFinder if
- You want the keyFinder feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches JavaScript
- You evaluated both and keyFinder 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 keyFinder
KeyFinder Passive API key and secret discovery for Chrome and Firefox KeyFinder is a browser extension for Chrome and Firefox that passively scans every page you visit for leaked API keys, tokens, secrets, and credentials. It runs silently in the background with zero configuration required. What It Detects KeyFinder ships with 80+ detection patterns covering secrets from: How It Works KeyFinder scans 10 different attack surfaces on every page: 1. Script src URLs Checks all script source URLs for keywords and tokens in query parameters 2. Inline scripts Scans tag contents for secret patterns 3. External scripts…
read the full keyFinder 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 keyFinder more popular?
chrome-devtools-mcp has 54,665 GitHub stars and keyFinder has 729. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and keyFinder free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and keyFinder under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and keyFinder?
chrome-devtools-mcp is written in TypeScript and keyFinder 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 keyFinder?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose keyFinder if its feature set, stack or MIT licence fits better. Both are self-hostable.