Firefox Bridge
Related Servers
Alternatives to Firefox Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to operate a real, logged-in Firefox session through an extension, including tab and history management, page reading, screenshots, and clicking, typing, or scrolling on domains the user approves.20 npmMIT
- AlicenseCqualityCmaintenanceEnables AI assistants to read and drive a real, logged-in Firefox browser, including tabs, cookies, history, and site interactions, all through the Model Context Protocol.5216 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to interact with the user's current Firefox or Chromium browser under per-site policies, allowing it to list tabs, read pages, take screenshots, fill fields, and click with user confirmation.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to drive a local Firefox browser: opening and managing tabs, navigating, reading page structure and text, clicking, typing, filling forms, running JavaScript, taking screenshots, and inspecting console messages and network requests. Everything runs over a local Unix socket with no network traffic, and actions are restricted to tabs explicitly placed under Claude's control.2 npmGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Firefox tabs, search browsing history, and read live webpage text and links with explicit per-domain user consent.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control existing Chrome and Firefox browser sessions locally, including tab management, navigation, form filling, screenshots, and persistent scripts, without remote relays or debugging ports.20 npm-
TDQS
Scored across 32 tools
Most tools target distinct browser actions or resources, but several near-duplicate pairs are easy to confuse: firefox_download vs firefox_downloads, firefox_history vs firefox_tab_history, firefox_tab_action vs firefox_release_tab, and firefox_read_page vs firefox_context vs firefox_inspect. Descriptions clarify these boundaries, but the large surface still creates meaningful misselection risk.
All names use a consistent firefox_ prefix and snake_case style. However, the set is not strictly verb_noun: several tools are noun-only resource names (firefox_bookmarks, firefox_history, firefox_frames, firefox_context, firefox_media), and there are minor singular/plural inconsistencies such as firefox_download vs firefox_downloads.
At 32 tools, the server is well above the typical well-scoped range and creates high cognitive load for an agent. The broad browser bridge domain explains some breadth, but ancillary capabilities such as media, tab groups, performance, network, and console could be consolidated or exposed more selectively.
The surface covers the core browser automation lifecycle: tab management, navigation, page reading, interaction, screenshots, waits, frames, downloads/uploads, bookmarks/history, and diagnostics. There are still minor gaps around dialog/alert handling, cookie or storage management, and drag-and-drop interactions.