head to head · open source
chrome-devtools-mcp vs jose
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. jose has 7,861 stars, 381 forks, 0 open issues and last shipped yesterday. chrome-devtools-mcp leads on adoption by 595% (54,665 vs 7,861 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; jose is written in TypeScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, jose 5%. jose 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 | jose | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 7.9K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 5.3K | ⑂ 381 |
| 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 jose if
- You want the jose feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and jose 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 jose
jose jose is a JavaScript module for JSON Object Signing and Encryption, providing support for JSON Web Tokens (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE), JSON Web Key (JWK), JSON Web Key Set (JWKS), and more. The module is designed to work across various Web interoperable runtimes including Node.js, browsers, Cloudflare Workers, Deno, Bun, and others. Sponsor If you want to quickly add JWT authentication to JavaScript apps, feel free to check out Auth0's JavaScript SDK and free plan. [Create an Auth0 account; it's free!][sponsor auth0] 💗 Help the project Support from the community to continue…
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 jose more popular?
chrome-devtools-mcp has 54,665 GitHub stars and jose has 7,861. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and jose free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and jose under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and jose?
chrome-devtools-mcp is written in TypeScript and jose 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 jose?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose jose if its feature set, stack or MIT licence fits better. Both are self-hostable.