head to head · open source
chrome-devtools-mcp vs competitive-companion
chrome-devtools-mcp has 52,222 GitHub stars, 4,037 forks, 109 open issues and last shipped today. competitive-companion has 1,310 stars, 211 forks, 90 open issues and last shipped 3 months ago. chrome-devtools-mcp leads on adoption by 3,886% (52,222 vs 1,310 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; competitive-companion is written in TypeScript under MIT. chrome-devtools-mcp has attracted 8% as many forks as stars, competitive-companion 16%. 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 8884 open source comparisons
Side by side
| chrome-devtools-mcp | competitive-companion | |
|---|---|---|
| GitHub stars | ★ 52K | ★ 1.3K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-09-18 | 2026-06-29 |
| Forks | ⑂ 4.0K | ⑂ 211 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick chrome-devtools-mcp if
- You weight community size — 52K 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 competitive-companion if
- You want the competitive-companion feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and competitive-companion fits your workflow better
About chrome-devtools-mcp
chrome devtools mcp is an Apache 2.0 TypeScript Model Context Protocol server, distributed on npm, that gives coding agents such as Claude, Cursor, Copilot and Antigravity control over and visibility into a live Chrome browser through the full Chrome DevTools toolset.
read the full chrome-devtools-mcp overview →
About competitive-companion
Competitive Companion [link cws]: [link amo]: [ ][link cws] [ ][link cws] [ ][link cws] [ ][link amo] [ ][link amo] [ ][link amo] A browser extension which parses competitive programming problems from various online judges (like AtCoder and Codeforces) and sends them to various tools (like CP Editor and CPH). Capable of parsing problems and contests and extracting data like the example testcases and the time and memory constraints. Install [ Chrome extension][link cws] [ ][link cws] [ Firefox add on][link amo] [ ][link amo] Tools that use Competitive Companion acmX AI Virtual Assistant Assistant.nvim AutoCp Caide…
read the full competitive-companion 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 competitive-companion more popular?
chrome-devtools-mcp has 52,222 GitHub stars and competitive-companion has 1,310. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and competitive-companion free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and competitive-companion under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and competitive-companion?
chrome-devtools-mcp is written in TypeScript and competitive-companion 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 competitive-companion?
Choose chrome-devtools-mcp if you want the larger community (52,222 stars) or its Apache-2.0 licence terms. Choose competitive-companion if its feature set, stack or MIT licence fits better. Both are self-hostable.