head to head · open source
chrome-devtools-mcp vs slate
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. slate has 31,747 stars, 3,306 forks, 653 open issues and last shipped 6 days ago. chrome-devtools-mcp leads on adoption by 72% (54,665 vs 31,747 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; slate is written in TypeScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, slate 10%. 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 | slate | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 32K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-10-28 |
| Forks | ⑂ 5.3K | ⑂ 3.3K |
| 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 slate if
- You want the slate feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and slate 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 slate
A completely customizable framework for building rich text editors. Why? · Principles · Demo · Examples · Documentation · Contributing! Slate lets you build rich, intuitive editors like those in Medium, Dropbox Paper or Google Docs—which are becoming table stakes for applications on the web—without your codebase getting mired in complexity. It can do this because all of its logic is implemented with a series of plugins, so you aren't ever constrained by what is or isn't in "core". You can think of it like a pluggable implementation of contenteditable built on top of React. It was inspired by libraries like…
read the full slate 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 slate more popular?
chrome-devtools-mcp has 54,665 GitHub stars and slate has 31,747. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and slate free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and slate under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and slate?
chrome-devtools-mcp is written in TypeScript and slate 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 slate?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose slate if its feature set, stack or MIT licence fits better. Both are self-hostable.