Add Edge browser support

[david-risney]

Is your feature request related to a problem? Please describe.

We field many requests from folks about how to use Chrome DevTools MCP with the Microsoft Edge browser. It would be great if we could make this easy to do by adding direct support for Edge in Chrome DevTools MCP.

Describe the solution you'd like

Add a --browser parameter that initially only supports default and chrome but that is extensible. Add support for declarative JSON files that describe chromium-based browser's install paths, user data directory, and URL schemes to be used to support additional browsers that can be selected with the --browser parameter. Per @natorion in this PR comment we don't want direct support for other browsers but might consider some kind of extensibility. Proof of concept diff.

Describe alternatives you've considered

Add a --browser=edge parameter to directly support Edge built-in to Chrome DevTools MCP. See proof of concept PR. Per @natorion we don't want to have support for non-Chrome browsers built-in to Chrome DevTools MCP so this isn't a great solution.

Additional context

No response

[david-risney]

I've made an incomplete change implementing extensibility support for additional browsers: main...david-risney:chrome-devtools-mcp:david-risney/browser-extensions. It is an incomplete draft of a possible direction for this feature to help with discussion. Happy to put more time into it if folks like the idea or direction.

The overall goal is to support reading browser definition JSON files that describe browser's URL schemes, executable paths, and so on and a new --browser argument to select one. This change adds a BrowserDefinition class that reads the browser definition JSON and has the various methods for determining if a URL is the new tab URL, resolving a channel to its executable path, and so on. There's a default hardcoded Chrome BrowserDefinition and then code for reading the JSON out of a chrome-devtools-mcp config folder.

[david-risney]

@natorion does this seem like the right direction regarding your comment How could this work as an extension of sorts? Thanks!

[natorion]

A few people are OOO right now, I will have to come back to you.

[natorion]

The current way to connect to any Chromium-based binary (like Edge - we also have seen Electron apps utilizing this) is through the command line parameter --executablePath. This should to work for Edge too.

At this point we are not planning to officially add an extension point to support non-Chrome browsers.

[qjkobe]

Hi @natorion ,
I think Edge support is very important. Chrome‘s profile doesn't have a nice profile-isolation machenism in Mac OS. Look at this screenshot:

But Edge will be very clean. In Chrome, I cannot choose my microsoft account automatically(It's outside 3). But in edge, it won't give that 3 suggestions.