head to head · open source
chrome-devtools-mcp vs archiveweb.page
chrome-devtools-mcp has 52,222 GitHub stars, 4,037 forks, 109 open issues and last shipped today. archiveweb.page has 1,575 stars, 111 forks, 111 open issues and last shipped 14 days ago. chrome-devtools-mcp leads on adoption by 3,216% (52,222 vs 1,575 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; archiveweb.page is written in TypeScript under AGPL-3.0. chrome-devtools-mcp has attracted 8% as many forks as stars, archiveweb.page 7%. 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 8884 open source comparisons
Side by side
| chrome-devtools-mcp | archiveweb.page | |
|---|---|---|
| GitHub stars | ★ 52K | ★ 1.6K |
| License | Apache-2.0 | AGPL-3.0 |
| Written in | TypeScript | TypeScript |
| Last push | 2026-09-18 | 2026-09-04 |
| Forks | ⑂ 4.0K | ⑂ 111 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick chrome-devtools-mcp if
- You weight community size — 52K 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 archiveweb.page if
- You want the archiveweb.page feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches TypeScript
- You evaluated both and archiveweb.page fits your workflow better
About chrome-devtools-mcp
chrome devtools mcp is an Apache 2.0 TypeScript Model Context Protocol server, distributed on npm, that gives coding agents such as Claude, Cursor, Copilot and Antigravity control over and visibility into a live Chrome browser through the full Chrome DevTools toolset.
read the full chrome-devtools-mcp overview →
About archiveweb.page
ArchiveWeb.page is a JavaScript based application for interactive, high fidelity web archiving that runs directly in the browser. The system can be used as a Chrome/Chromium based browser extension and also as a standalone Electron app. The system creates, stores, and replays high fidelity web archives stored directly in the browser's storage (via IndexedDB). For more detailed info on how to use the extension and standalone app, see the ArchiveWeb.page User Guide. The browser extension is available on the Chrome Web Store. Downloads for the desktop are are available on the GitHub Releases page. Architecture The e…
read the full archiveweb.page 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 archiveweb.page more popular?
chrome-devtools-mcp has 52,222 GitHub stars and archiveweb.page has 1,575. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and archiveweb.page free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and archiveweb.page under AGPL-3.0. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and archiveweb.page?
chrome-devtools-mcp is written in TypeScript and archiveweb.page 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 archiveweb.page?
Choose chrome-devtools-mcp if you want the larger community (52,222 stars) or its Apache-2.0 licence terms. Choose archiveweb.page if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.