head to head · open source
chrome-devtools-mcp vs slugify
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. slugify has 2,710 stars, 102 forks, 2 open issues and last shipped 2 months ago. chrome-devtools-mcp leads on adoption by 1,917% (54,665 vs 2,710 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; slugify is written in JavaScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, slugify 4%. 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 | slugify | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 2.7K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | JavaScript |
| Last push | 2026-11-02 | 2026-09-18 |
| Forks | ⑂ 5.3K | ⑂ 102 |
| 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 slugify if
- You want the slugify feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches JavaScript
- You evaluated both and slugify 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 slugify
slugify Slugify a string Useful for URLs, filenames, and IDs. It handles most major languages, including German (umlauts), Vietnamese, Arabic, Russian, and more. Install Usage API slugify(string, options?) string Type: string String to slugify. options Type: object separator Type: string \ Default: ' ' lowercase Type: boolean \ Default: true Make the slug lowercase. decamelize Type: boolean \ Default: true Convert camelcase to separate words. Internally it does fooBar → foo bar . customReplacements Type: Array \ Default: [ ['&', ' and '], ['🦄', ' unicorn '], ['♥', ' love '] ] Add your own custom replacements…
read the full slugify 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 slugify more popular?
chrome-devtools-mcp has 54,665 GitHub stars and slugify has 2,710. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and slugify free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and slugify under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and slugify?
chrome-devtools-mcp is written in TypeScript and slugify in JavaScript. 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 slugify?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose slugify if its feature set, stack or MIT licence fits better. Both are self-hostable.