head to head · open source
chrome-devtools-mcp vs docx
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. docx has 5,982 stars, 621 forks, 162 open issues and last shipped yesterday. chrome-devtools-mcp leads on adoption by 814% (54,665 vs 5,982 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; docx is written in TypeScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, docx 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 | docx | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 6.0K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 5.3K | ⑂ 621 |
| 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 docx if
- You want the docx feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and docx 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 docx
Easily generate and modify .docx files with JS/TS. Works for Node and on the Browser. [![NPM version][npm image]][npm url] [![Downloads per month][downloads image]][downloads url] [![GitHub Action Workflow Status][github actions workflow image]][github actions workflow url] [![Known Vulnerabilities][snky image]][snky url] [![PRs Welcome][pr image]][pr url] [![codecov][codecov image]][codecov url] [![Docx.js Editor][docxjs editor image]][docxjs editor url] Demo Browser Here are examples of docx being used with basic HTML/JS in a browser environment: Here are examples of docx working in Angular : Here are examples…
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 docx more popular?
chrome-devtools-mcp has 54,665 GitHub stars and docx has 5,982. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and docx free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and docx under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and docx?
chrome-devtools-mcp is written in TypeScript and docx 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 docx?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose docx if its feature set, stack or MIT licence fits better. Both are self-hostable.