head to head · open source
chrome-devtools-mcp vs Harper
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. Harper has 17,365 stars, 794 forks, 896 open issues and last shipped yesterday. chrome-devtools-mcp leads on adoption by 215% (54,665 vs 17,365 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; Harper is written in Rust under Apache-2.0. chrome-devtools-mcp has attracted 10% as many forks as stars, Harper 5%. Harper 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 | Harper | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 17K |
| License | Apache-2.0 | Apache-2.0 |
| Written in | TypeScript | Rust |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 5.3K | ⑂ 794 |
| 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 Harper if
- You want the Harper feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Rust
- You evaluated both and Harper 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 Harper
Harper Harper is an English grammar checker designed to be just right. I created it after years of dealing with the shortcomings of the competition. Grammarly was too expensive and too overbearing. Its suggestions lacked context, and were often just plain wrong . Not to mention: it's a privacy nightmare. Everything you write with Grammarly is sent to their servers. Their privacy policy claims they don't sell the data, but that doesn't mean they don't use it to train large language models and god knows what else. Not only that, but the round trip time of the network request makes revising your work all the more…
read the full Harper 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 Harper more popular?
chrome-devtools-mcp has 54,665 GitHub stars and Harper has 17,365. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and Harper free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and Harper under Apache-2.0. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and Harper?
chrome-devtools-mcp is written in TypeScript and Harper in Rust. 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 Harper?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose Harper if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.