head to head · open source
chrome-devtools-mcp vs Screenity
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. Screenity has 18,894 stars, 1,538 forks, 8 open issues and last shipped 9 days ago. chrome-devtools-mcp leads on adoption by 189% (54,665 vs 18,894 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; Screenity is written in JavaScript under GPL-3.0. chrome-devtools-mcp has attracted 10% as many forks as stars, Screenity 8%. 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 | Screenity | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 19K |
| License | Apache-2.0 | GPL-3.0 |
| Written in | TypeScript | JavaScript |
| Last push | 2026-11-02 | 2026-10-25 |
| Forks | ⑂ 5.3K | ⑂ 1.5K |
| 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 Screenity if
- You want the Screenity 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 Screenity 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 Screenity
Screenity ✨ Screenity's open source work is sponsored by Recall.ai API for desktop recording If you’re looking for a hosted desktop recording API, consider checking out Recall.ai, an API that records Zoom, Google Meet, Microsoft Teams, in person meetings, and more. The free and privacy friendly screen recorder with no limits 🎥 Get it now it's free! Screenity is a powerful privacy friendly screen recorder and annotation tool to make better videos for work, education, and more. You can create stunning product demos, tutorials, presentations, or share feedback with your team all for free. Want to support the…
read the full Screenity 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 Screenity more popular?
chrome-devtools-mcp has 54,665 GitHub stars and Screenity has 18,894. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and Screenity free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and Screenity under GPL-3.0. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and Screenity?
chrome-devtools-mcp is written in TypeScript and Screenity 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 Screenity?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose Screenity if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.