firefox-devtools-mcp
Related Servers
Alternatives to firefox-devtools-mcp
- AlicenseCqualityDmaintenanceProvides Firefox browser automation capabilities through Playwright, allowing control of Firefox from MCP-enabled applications with features for basic automation and advanced multi-tab debugging.2929MIT
Related Servers
- FlicenseAqualityBmaintenanceModel Context Protocol server for automating Firefox via WebDriver BiDi, enabling page navigation, snapshots, input, network monitoring, and console debugging for AI agents in MCP clients.315,265 npm-
- AlicenseBqualityBmaintenanceEnables AI agents to drive a user-launched Firefox instance via its native Marionette protocol, providing precise DOM actuation like clicking, typing, uploading files, taking screenshots, and evaluating JavaScript.189 npm1GPL 2.0
- AlicenseAqualityCmaintenanceDrive Firefox-based browsers (Floorp, LibreWolf, Zen, Waterfox, Mullvad, Firefox) from any MCP client — read pages, screenshot, click, fill forms and manage tabs in your real session, over Marionette/WebDriver. OS input & JS eval locked by default.4160 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP client to drive a real, already-logged-in Firefox session through a WebExtension rather than a WebDriver connection, so tabs, cookies and logins work as-is without relaunching the browser under remote-control flags. Exposes tools for tab listing and selection, navigation, accessibility-style snapshots, clicking, filling, typing, key presses, file uploads, screenshots and waiting, with per-origin permission grants and opt-in script evaluation.MIT
- AlicenseBqualityCmaintenanceLets Claude Code attach to a running, signed-in Firefox over WebDriver BiDi to control tabs, navigate, screenshot, read pages, click, type, fill forms, evaluate JavaScript, and inspect console/network activity.22MIT
- FlicenseNot gradedqualityBmaintenanceLocal-first browser automation for LibreWolf, enabling controlled profile browsing with status, navigation, screenshots, console/network inspection, and more through MCP.-
TDQS
Scored across 35 tools
Every tool targets a distinct action or resource, with descriptions explicitly clarifying potential overlaps like press_key vs type_text, take_snapshot vs evaluate_script, and screenshot_page vs screenshot_by_uid. No two tools are indistinguishable.
Nearly all tools follow a snake_case verb_noun pattern (e.g., list_pages, click_by_uid, install_extension). Minor deviations exist: screencast_start/stop use noun_verb order, and new_page is adjective_noun, but overall the naming is highly consistent.
With 35 tools, the set exceeds the 25+ threshold for 'too many' and feels heavy for a browser automation server. While the domain is broad, several tools (e.g., accept_dialog/dismiss_dialog, clear_snapshot, clear_downloads) could be consolidated or grouped, making the count excessive.
The surface covers page management, element interaction, forms, downloads, extensions, screencasts, and script evaluation. Minor gaps exist for iframe/frame switching, cookie/storage management, and explicit wait tools, but these can be worked around via evaluate_script.