The functionality seems to overlap with the Playwright MCP server [0]. I've been using this instead of the built in browsers in Claude Code and Codex since it lets you grant access to pages and sessions that are already open. Of course one should be weary of the lethal trifecta when using these tools and use separate profiles for them.
It is a chromium extension and Firefox is not a chromium-based browser.
Like or dislike Firefox, omitting it from a list called "real browser" just looks amateur or sloppy. How about "real chromium browser"? Was it really that hard?
It's all right when it works, but it has a habit of disconnecting; you have to rerun 'browse pair'. This MCP should hopefully become unnecessary once OpenCode's integrated browser tool gains persistent sessions. https://github.com/anomalyco/opencode/pull/63002
OpenCode comes with the cost too. The cost of the hosted version is on par with cloud hosted proprietary models. And we cannot simply run the LLMs on every laptop. Given this, how do we us the browse efficiently?
The functionality seems to overlap with the Playwright MCP server [0]. I've been using this instead of the built in browsers in Claude Code and Codex since it lets you grant access to pages and sessions that are already open. Of course one should be weary of the lethal trifecta when using these tools and use separate profiles for them.
[0] https://playwright.dev/docs/getting-started-mcp
Also we have Chrome's official https://github.com/ChromeDevTools/chrome-devtools-mcp
> Your real browser: Chrome, Edge, Brave, Arc, Helium, Vivaldi, Opera and Chromium.
Firefox not?
Firefox is not a real browser, it does not even support CDP.
Well, it's an extension, so the api surface is different on FF. So it's not just a matter of them not listing it.
Looks like they only target Chromium-based browsers with their extension.
It is a chromium extension and Firefox is not a chromium-based browser.
Like or dislike Firefox, omitting it from a list called "real browser" just looks amateur or sloppy. How about "real chromium browser"? Was it really that hard?
why not https://github.com/ChromeDevTools/chrome-devtools-mcp
It's all right when it works, but it has a habit of disconnecting; you have to rerun 'browse pair'. This MCP should hopefully become unnecessary once OpenCode's integrated browser tool gains persistent sessions. https://github.com/anomalyco/opencode/pull/63002
OpenCode comes with the cost too. The cost of the hosted version is on par with cloud hosted proprietary models. And we cannot simply run the LLMs on every laptop. Given this, how do we us the browse efficiently?
you don't have to use their hosted models, nor their agent, for that matter
was this comment made by literally looking at the url? XD