[meta] Refactor firefox-devtool-mcp to only use WebDriver BiDi
Categories
(Developer Infrastructure :: Firefox MCP, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Unassigned)
References
(Depends on 5 open bugs, Blocks 4 open bugs)
Details
(Keywords: meta, Whiteboard: [meta])
At the moment firefox-devtools-mcp relies on selenium which uses both WebDriver Classic and BiDi.
To have a better control over the features available to the MCP it would be beneficial to drop the Selenium layer and directly create a WebDriver BiDi Session.
| Reporter | ||
Comment 1•6 months ago
|
||
The main blocker to switch to BiDi 100% is that all commands which work today against privileged contexts in WebDriver Classic will need to have an equivalent in BiDi.
At the moment we can already evaluate scripts against chrome contexts in BiDi but we also need to be able to take screenshots, send actions etc...
| Reporter | ||
Comment 2•6 months ago
|
||
I had a branch to switch to BiDi already at https://github.com/juliandescottes/firefox-devtools-mcp/tree/switch-bidi-old but this is based on a much older version of the mcp.
I also had a basic bidi node client at https://github.com/juliandescottes/firefox-bidi-client which was extracted from the MCP.
| Reporter | ||
Comment 3•2 months ago
|
||
Let's make this a meta and start filing individual bugs per module / group of tools to migrate.
| Reporter | ||
Updated•1 month ago
|
Description
•