head to head · open source
chrome-devtools-mcp vs ws-scrcpy
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. ws-scrcpy has 2,594 stars, 577 forks, 91 open issues and last shipped 3 days ago. chrome-devtools-mcp leads on adoption by 2,007% (54,665 vs 2,594 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; ws-scrcpy is written in TypeScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, ws-scrcpy 22%. 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 | ws-scrcpy | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 2.6K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-10-31 |
| Forks | ⑂ 5.3K | ⑂ 577 |
| 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 ws-scrcpy if
- You want the ws-scrcpy feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and ws-scrcpy 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 ws-scrcpy
ws scrcpy Web client for [Genymobile/scrcpy][scrcpy] and more. Requirements Browser must support the following technologies: WebSockets Media Source Extensions and h264 decoding; WebWorkers WebAssembly Server: Node.js v10+ node gyp (installation) adb executable must be available in the PATH environment variable Device: Android 5.0+ (API 21+) Enabled adb debugging On some devices, you also need to enable an additional option to control it using keyboard and mouse. Build and Start Make sure you have installed node.js, node gyp and build tools Supported features Android Screen casting The modified [version][fork]…
read the full ws-scrcpy 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 ws-scrcpy more popular?
chrome-devtools-mcp has 54,665 GitHub stars and ws-scrcpy has 2,594. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and ws-scrcpy free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and ws-scrcpy under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and ws-scrcpy?
chrome-devtools-mcp is written in TypeScript and ws-scrcpy 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 ws-scrcpy?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose ws-scrcpy if its feature set, stack or MIT licence fits better. Both are self-hostable.