Skip to main content
Glama

Related Servers

Alternatives to Firefox MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      C
      maintenance
      Enables 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.
      52
      16 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Let AI agents use the Firefox, Zen, or LibreWolf browser you already have open, with your logins, cookies, and extensions intact. No Playwright, Chromium, or WebDriver. Agents work in background tabs while you keep browsing: read pages, click, fill forms, take screenshots, and capture network traffic. A WebExtension plus a local bridge lets several agents share one browser.
      14
      297 PyPI
      40
      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
      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.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage Firefox tabs, search browsing history, and read live webpage text and links with explicit per-domain user consent.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Connects an AI assistant to a local Firefox session so it can read pages, interact with forms, manage tabs, and investigate browser issues under user-controlled access rules.
      32
      MIT

    TDQS

    A3.5/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs (navigation, DOM interaction, screenshots, downloads, dialogs, viewport, extensions, screencasts). There is mild overlap between fill_by_uid/type_text/fill_form_by_uid and between get_page_text/take_snapshot/evaluate_script, but descriptions explicitly steer the agent toward the right one in each case.

    Naming Consistency4/5

    Names are overwhelmingly consistent snake_case verb_noun (list_pages, navigate_page, close_page, take_snapshot, click_by_uid, set_viewport_size). Minor deviations like new_page (instead of create_page) and the take_/get_ verb mix for content retrieval are readable and do not break the pattern.

    Tool Count3/5

    35 tools is on the heavy side for a single server, though the breadth of a full browser-automation surface (tabs, DOM, forms, screenshots, downloads, dialogs, extensions, screencasts) justifies most of them. It is borderline: the surface could be trimmed or grouped without losing capability, so a heavy-but-defensible score.

    Completeness4/5

    Covers the browser lifecycle very thoroughly: page CRUD, navigation, DOM interaction, forms, uploads, downloads, dialogs, viewport, extension management, screencasts, JS eval, and process info/output. Minor gaps remain—uninstall_extension references a list_extensions tool that isn't present, and there is no explicit wait-for-condition or cookie/storage management.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data