Skip to main content
Glama

Related Servers

Alternatives to FoxBridge MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect and control open Firefox tabs through the Model Context Protocol, including reading page content, filling forms, clicking elements, taking screenshots, and using native WebDriver BiDi input and diagnostics.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes Firefox browser automation capabilities through the Model Context Protocol, enabling AI assistants to control web browsers for navigation, interaction, and data collection tasks.
      4
      BSD 3-Clause
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      12 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read and control the user's real Firefox-based browser using existing logins, cookies, and open tabs, while restricting access to only the windows, tabs, rights, and time the user explicitly grants.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to control the user's installed Firefox with real logins, saved passwords, bookmarks, and extensions while offering all Playwright MCP tools and options. It runs on a copied profile so the daily browser remains untouched and supports multiple profiles or accounts.
      25
      MIT

    TDQS

    C2.9/5.0

    Scored across 52 tools

    Disambiguation2/5

    Many tools have overlapping purposes, especially between ff_ prefixed (real Firefox) and non-prefixed (browser instance) versions, e.g., click vs ff_click, navigate vs ff_navigate, and multiple cookie-related tools. Agents may easily misselect.

    Naming Consistency2/5

    Naming conventions are mixed: some use snake_case (browser_start, clear_cookies), some use ff_ prefix (ff_click), and some are simple verbs (click, hover). No consistent pattern across the tool set.

    Tool Count3/5

    52 tools is high but justified by comprehensive browser automation scope. However, many tools are duplicated for two execution contexts (real Firefox vs. clean instance), which could be consolidated.

    Completeness4/5

    Covers a wide range of browser interactions: navigation, clicking, typing, cookies, storage, history, bookmarks, network, downloads, tabs. Missing bookmark creation/deletion but overall very complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues