Skip to main content
Glama
leetomo2528

firefox-use

by leetomo2528
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to firefox-use

No user-submitted related servers found.

    Related Servers

    • firefox-mcp

      surpasses
      A
      license
      B
      quality
      C
      maintenance
      Lets 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.
      22
      MIT

    • Controlium

      am-will
      A
      license
      Not graded
      quality
      B
      maintenance
      Chrome extension + MCP bridge that gives Claude control over your real browser via CDP, enabling navigation, clicking, typing, scrolling, screenshots, and JS execution with a visible cursor and tab-bring-to-front.
      1
      MIT

    • chromium-bridge

      dashi96
      A
      license
      A
      quality
      B
      maintenance
      MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code. 18 browser automation tools (navigate, click, forms, screenshots, GIF recording, console, network) plus a popup chat panel powered by the Claude Agent SDK.
      18
      7
      MIT

    • gotham-browser

      gotham-os
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to control a real browser using AI for web scraping, competitive intelligence, and UX auditing through the MCP protocol.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools are clearly separated by role: tab management, page reading, form input, file handling, network/console logging, and Firefox maintenance. The main overlap is that tabs_context_mcp and firefox_status both report the session's tab list, and read_page, find, and get_page_text have somewhat similar page-reading purposes even though the descriptions distinguish them well.

    Naming Consistency2/5

    Although most names use snake_case, there is no consistent pattern across the set. Tab tools use an odd _mcp suffix, several tools are bare or generic nouns like find, computer, and gif_creator, and there is no uniform verb_noun or noun_verb convention across the rest. A new agent cannot reliably guess related tools from their names.

    Tool Count3/5

    20 tools is on the heavy side and somewhat at the edge where complexity starts to overwhelm. The count reflects a broad browser-automation scope, but some responsibilities are spread across multiple tools rather than being consolidated, so the set feels larger than necessary even though it is not unreasonable.

    Completeness4/5

    The tool surface covers a nearly complete browser workflow: tabs, navigation, reading and finding elements, form input, file and image uploads, screenshots, keyboard/pointer control, JS evaluation, console and network logging, GIF capture, and Firefox restart/dialog handling. Missing pieces like cookie/storage management or explicit screenshot download are minor and usually workable with changes or extensions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources