ChromeDevTools
Support Chrome forks
Is your feature request related to a problem? Please describe.
I just installed this MCP server for Claude Code. My system has Chrome, which I use for many things, Brave, which I use just for avoiding YouTube ads, and I've started using Comet+Perplexity in my work environment. Chromium lurks as well, for when I need a "like Chrome but not" for testing.
When I ask for information about what a browser is doing, the system always starts a new Chrome, and it's a curious thing, in that it lacks access to any of my profiles.
Describe the solution you'd like
I would like to be able to select any Chrome compatible browser, in particular there should be support for launching a non-default browser.
Either prior to or after launch we should have the option to pick which profile is to be used.
it would be great if there were a way to configure command line options for the invocation - so we can decide to use an http or SOCKS5 proxy as part of a debugging process.
Describe alternatives you've considered
Not sure what to say here, if this is going to be a Chrome friendly MCP, it should cover all of Chromedom, not just the one browser.
Additional context
No response
We are only supporting Chrome officially. You can point the MCP server to any binary though. Please take a look at --browser-url and --executable-path command line parameters as mentioned in https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=readme-ov-file#configuration.
If the target speaks the right and up-to-date CDP (meaning, what Chrome and Chromium vanilla speaks) it ought to work.
