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

    • Kamurafox

      GabrielKamura
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      1 npm
      GPL 3.0

    • 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
      D
      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
    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.2/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: reading console vs network traffic, page dumps (read_page) vs language search (find) vs prose extraction (get_page_text), and local-file upload (file_upload) vs session-image insert (upload_image) are all cleanly separated by their descriptions. The action tools (computer, form_input, javascript_tool, navigate) target different interaction modes without overlap.

    Naming Consistency3/5

    Most names follow a verb_noun pattern (read_console_messages, resize_window, file_upload, form_input), but the set mixes in bare single words (navigate, find, computer), a firefox_ prefix (firefox_restart, firefox_dialog, firefox_status), and a _mcp suffix on tabs tools (tabs_create_mcp, tabs_close_mcp, tabs_context_mcp). Still readable but clearly inconsistent conventions.

    Tool Count4/5

    20 tools is on the heavy side but each earns its place across tab management, page reading, interaction, input, batching and browser control. This is a broad browser-automation surface where the count is justified rather than padded.

    Completeness4/5

    Covers the core lifecycle well: tab create/close/list, navigation, accessibility-tree and text reading, element finding, JS execution, form filling, file/image upload, console/network inspection, dialogs, resize and restart. Minor gaps like cookie/storage management or a dedicated download handler are workable around via javascript_tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources