head to head · open source

chrome-devtools-mcp vs browser-agent

chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. browser-agent has 4,138 stars, 245 forks, 34 open issues and last shipped 9 months ago. chrome-devtools-mcp leads on adoption by 1,221% (54,665 vs 4,138 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; browser-agent is written in TypeScript under Apache-2.0. chrome-devtools-mcp has attracted 10% as many forks as stars, browser-agent 6%. 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.

chrome-devtools-mcp ★ 55K browser-agent ★ 4.1K category Productivity & Utilities

← all 20902 open source comparisons

Side by side

chrome-devtools-mcp browser-agent
GitHub stars ★ 55K ★ 4.1K
License Apache-2.0 Apache-2.0
Written in TypeScript TypeScript
Last push 2026-11-02 2026-02-08
Forks ⑂ 5.3K ⑂ 245
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

full chrome-devtools-mcp profile →

pick browser-agent if

  • You want the browser-agent feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches TypeScript
  • You evaluated both and browser-agent fits your workflow better

full browser-agent profile →

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 browser-agent

🚀 New: Magnitude is state of the art, scoring 94% on WebVoyager! Magnitude uses vision AI to enable you to control your browser with natural language. 🧭 Navigate Sees and understands any interface to plan out actions 🖱️ Interact Executes precise actions using mouse and keyboard 🔍 Extract Intelligently extracts useful structured data ✅ Verify Built in test runner with powerful visual assertions You can use it to automate tasks on the web, integrate between apps without APIs, extract data, test your web apps, or as a building block for your own browser agents. ↕️ Magnitude in action! ↕️ Get started Running…

read the full browser-agent 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 browser-agent more popular?

chrome-devtools-mcp has 54,665 GitHub stars and browser-agent has 4,138. chrome-devtools-mcp has the larger community by that measure.

Are chrome-devtools-mcp and browser-agent free?

Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and browser-agent under Apache-2.0. Neither carries a licence fee.

What is the difference between chrome-devtools-mcp and browser-agent?

chrome-devtools-mcp is written in TypeScript and browser-agent 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 browser-agent?

Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose browser-agent if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.