head to head · open source
chrome-devtools-mcp vs EhSyringe
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. EhSyringe has 3,764 stars, 122 forks, 14 open issues and last shipped 28 days ago. chrome-devtools-mcp leads on adoption by 1,352% (54,665 vs 3,764 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; EhSyringe is written in TypeScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, EhSyringe 3%. 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 | EhSyringe | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 3.8K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-10-06 |
| Forks | ⑂ 5.3K | ⑂ 122 |
| 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 EhSyringe if
- You want the EhSyringe feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and EhSyringe 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 EhSyringe
EhSyringe E 站注射器，将中文翻译注入到 E 站体内。 这一针打下去你就会说中文了。 安装 Chrome 安装方法 1. 前往 Release 页面下载 zip 文件并解压 2. 打开 Chrome 扩展程序管理器 chrome://extensions 3. 勾选 开发者模式 4. 点击 加载已解压的扩展程序 ，选择本扩展所在目录 Firefox 安装方法 1. 前往 Release 页面下载 xpi 文件 2. 安装 Firefox 的延长支持版（ESR）、开发者版或 Nightly 版 3. 打开 Firefox 配置编辑器（ about:config 页），搜索 xpinstall.signatures.required 并将值设置为 false 4. 打开 Firefox 附加组件管理器 about:addons ，点击右上角设置菜单，选择“从文件安装附加组件”，选择下载的 xpi 文件 参考 Firefox 中的附加组件签名 用户脚本（UserScript）安装方法 1. 安装一个用户脚本管理器 2. 前往 Sleazy Fork 安装最新版本 也可以从 GitHub Release 安装 如果你使用的是 Via、Alook 等对用户脚本支持不完善的浏览器，可以考虑使用以下代码加载插件 功能 全站翻译（大部分） 标签翻译 标签介绍 标签翻译数据更新（当前数据库包含 条标签翻译） 搜索框标签输入提示…
read the full EhSyringe 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 EhSyringe more popular?
chrome-devtools-mcp has 54,665 GitHub stars and EhSyringe has 3,764. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and EhSyringe free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and EhSyringe under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and EhSyringe?
chrome-devtools-mcp is written in TypeScript and EhSyringe 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 EhSyringe?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose EhSyringe if its feature set, stack or MIT licence fits better. Both are self-hostable.