Skip to main content
Glama
Sign In
firefox-mcp

firefox-mcp

by surpasses
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to firefox-mcp

No user-submitted related servers found.

    Related Servers

    • Kamurafox

      GabrielKamura
      A
      license
      Not graded
      quality
      B
      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.
      8 npm
      GPL 3.0

    • claude-for-firefox

      sidneysimas
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to control the user's real Firefox browser through a local MCP server, with tools for tabs, navigation, page reading, clicking, typing, forms, screenshots, and file uploads under per-site consent.
      8 npm
      MIT

    • claude-for-firefox

      rorsketch
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to drive a real Firefox browser through a local MCP server using synthetic DOM events for clicks and typing. Supports tab management, navigation, page reading, form interaction, screenshots, and per-site consent with no network port opened.
      8 npm
      1
      MIT

    • zen-browser

      grapedjuice
      A
      license
      B
      quality
      B
      maintenance
      Lets Claude Code see and drive a real Zen or Firefox browser session: listing and switching tabs, navigating, clicking, typing, scrolling, filling forms, taking screenshots, reading page content, and inspecting console and network logs. Actions target tabs the user is already signed in to, with an in-page stop control and activity popup for oversight.
      15
      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

    B3.4/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct browser automation concern—tab management, navigation, element discovery, input, scrolling, and diagnostics—so an agent can reliably select the right one. Even similar tools like read_page and find have clear separation: one lists elements, the other searches by selector/text. No two tools appear to do the same job.

    Naming Consistency3/5

    Naming is readable but mixes conventions: tabs_* forms a clear prefix group, read_* and get_* group read operations, while interaction tools use bare verbs like click, type, scroll, and hover. This category-based pattern is understandable but not a uniform verb_noun convention.

    Tool Count3/5

    At 22 tools, the set is comprehensive but on the heavy side, falling into the borderline range for a single server. Most tools are individually justified for browser automation, yet some input-related tools (type, form_input, press_key) could potentially be consolidated.

    Completeness4/5

    The surface covers tab lifecycle, navigation, element interaction, scrolling, screenshots, scripting, and diagnostics, which is strong coverage for browser automation. Minor gaps like explicit cookie management, file upload, or waiting for a specific element exist, but agents can work around them with evaluate and wait.

    Resources