head to head · open source
chrome-devtools-mcp vs plasmo
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. plasmo has 13,172 stars, 466 forks, 371 open issues and last shipped 3 days ago. chrome-devtools-mcp leads on adoption by 315% (54,665 vs 13,172 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; plasmo is written in TypeScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, plasmo 4%. 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 | plasmo | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 13K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-10-31 |
| Forks | ⑂ 5.3K | ⑂ 466 |
| 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 plasmo if
- You want the plasmo feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and plasmo 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 plasmo
English 简体中文 Tiếng Việt Deutsch French Indonesian Русский Turkish 日本語 한국어 Production Cloud: We've built a cloud offering for browser extensions called Itero. Check it out if you want instant beta testing and more awesome features. Plasmo Framework The Plasmo Framework is a battery packed browser extension SDK made by hackers for hackers. Build your product and stop worrying about config files and the odd peculiarities of building browser extensions. It's like Next.js for browser extensions! Highlighted Features First class React + Typescript Support Declarative Development Content Scripts UI Tab Pages Live…
read the full plasmo 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 plasmo more popular?
chrome-devtools-mcp has 54,665 GitHub stars and plasmo has 13,172. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and plasmo free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and plasmo under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and plasmo?
chrome-devtools-mcp is written in TypeScript and plasmo 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 plasmo?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose plasmo if its feature set, stack or MIT licence fits better. Both are self-hostable.