chrome-devtools-mcp vs browser-harness
chrome-devtools-mcp is the more adopted project, with 54,058 GitHub stars against 18,585 for browser-harness (about 2.9x more). browser-harness was updated more recently (today, against yesterday). chrome-devtools-mcp is written in TypeScript and browser-harness in Python.
| chrome-devtools-mcp | browser-harness | |
|---|---|---|
| Description | Chrome DevTools for coding agents | Let Claude Code, Codex or Cursor use your real Chrome, logged in as you. One prompt to set up. Open source, MIT. |
| Author | ChromeDevTools | browser-use |
| Stars | 54058 | 18585 |
| Language | TypeScript | Python |
| License | Apache-2.0 | MIT |
| Last update | 2026-10-23T14:15:34Z | 2026-10-24T01:48:48Z |
| Source | https://github.com/ChromeDevTools/chrome-devtools-mcp | https://github.com/browser-use/browser-harness |
| Stars this week | +343 | +117 |
Which should you choose?
- chrome-devtools-mcp describes itself as: "Chrome DevTools for coding agents"
- browser-harness describes itself as: "Let Claude Code, Codex or Cursor use your real Chrome, logged in as you. One prompt to set up. Open source, MIT."
Stars measure adoption, not fit. Read both READMEs for the tools each server exposes, then try them side by side in your client: the install guide shows how to add both.
Frequently asked questions
Which is more popular, chrome-devtools-mcp or browser-harness?
chrome-devtools-mcp has more GitHub stars: 54,058 against 18,585. This week chrome-devtools-mcp gained 343 stars and browser-harness gained 117, which says more about current momentum than the all-time total. Both figures are refreshed daily from GitHub.
Are chrome-devtools-mcp and browser-harness open source?
chrome-devtools-mcp: Apache-2.0 (open source). browser-harness: MIT (open source). An open-source license lets you run and self-host the server at no cost. If either one wraps a commercial API, that provider's pricing still applies, so read each README for the accounts and keys it needs.
Can I use chrome-devtools-mcp and browser-harness together?
Yes, if both run as MCP servers. MCP clients such as Claude Code, Cursor and VS Code can connect to several servers at once, and the agent picks tools from each. Give them distinct names in your config, and keep the number of active servers small so tool definitions do not crowd the context window.
Related comparisons
- browser-use vs chrome-devtools-mcp
- browser-use vs browser-harness
- chrome-devtools-mcp vs payload
- chrome-devtools-mcp vs UI-TARS-desktop
- chrome-devtools-mcp vs invisible_dots
- chrome-devtools-mcp vs quasar
- chrome-devtools-mcp vs codex-chatgpt-web
- payload vs browser-harness
chrome-devtools-mcp details · browser-harness details · All Browser Automation MCP servers
Data last updated . Stars and downloads are refreshed every day from GitHub and npm.