chrome-devtools-mcp

I have been using Chrome's official MCP devtools server since Nov 2025. https://github.com/ChromeDevTools/chrome-devtools-mcp Before that I used Chrome web drivers but MCP is faster and more capable. I also instruct LLMs to test my pages on Firefox using its official MCP to make sure they work in Firefox too: https://github.com/mozilla/firefox-devtools-mcp Now I will add Safari to the compatibility tests. cool

Chrome Devtools MCP now has an (experimental) CLI as well and can produce neat things like Lighthouse Audits. https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1... I've only used it a bit, but it's working well so far.

The DevTools MCP project just recently landed a standalone CLI: https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/m... Great news to all of us keenly aware of MCP's wild token costs. ;) The CLI hasn't been announced yet (sorry guys!), but it is shipping in the latest v0.20.0 release. (Disclaimer: I used to work on the DevTools team. And I still do, too)

Rod seems to be about automating the local browser itself via MCP, through which you can try to self-automate websites loaded in the browser. Interestingly, it seems Google nowadays has its own official implementation of this https://github.com/ChromeDevTools/chrome-devtools-mcp WebMCP seems to be about the authors of websites being able to publish a list of custom built-in tools the page has available for LLM agents to call. Less like "Analyze the form elements and call the DOM APIs to set..." and more akin to "Call the submitInformation(...) tool the website told us about over WebMCP".

Gemini CLI can also control a browser: https://github.com/ChromeDevTools/chrome-devtools-mcp

Jump the line and just install it. who needs to read stuff. https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=re...

I've had good success with the Chrome devtools MCP (https://github.com/ChromeDevTools/chrome-devtools-mcp) for browser automation with Gemini CLI, so I'm guessing this model will work even better.

Most browsers these days expose a control API (like ChromeDevtools Protocol MCP [1]) that open up a socket API and can take in json instructions for bidirectional communication. Chrome is the gold standard here but both Safari and Firefox have their own driver. For you existing browser session you'd have to start it already with open socket connection as by default that's not enabled but once you do the server should able to find an open local socket and connect to it and execute controls. worth nothing that this "control browser" hype is quite deceiving and it doesn't really work well imo because LLMs still suck at understanding the DOM so you need various tricks to optimize for that so I would take OP's claims with a giant bag of salt. Also these automations are really easy to identify and block as they are not organic inputs so the act

I'd recommend the chrome-devtools-mcp for that: https://github.com/ChromeDevTools/chrome-devtools-mcp/ It's pretty new, but so far it's been a lifesaver.