Skip to main content
Glama

Related Servers

Alternatives to Zamery Browser

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access individual Firefox tabs in their real logged-in state with time-limited, clearly marked, and revocable sharing. Supports both view-only and full-control modes, including interaction, navigation, and automation of the shared tab.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets an MCP client list and read pages a user has explicitly shared from a running Firefox session, including visible job listings and recruiter conversations, and search for text within those pages. Access is read-only, granted per page for 30 minutes from the toolbar, and ends on navigation, reload, tab closure, revocation, or client disconnect.
      MIT
    • 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
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Codex to manage a local Firefox session by listing, grouping, opening, activating, navigating, and closing non-private tabs and native tab groups through a secure local native-messaging bridge.
      MIT
    • A
      license
      Not graded
      quality
      B
      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.
      13 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target a distinct resource or action and descriptions go out of their way to delineate boundaries (e.g. fill replaces vs type inserts at caret). A few pairs could still be confused: browser_contexts vs browser_status (both report shared tabs), browser_groups vs browser_contexts, and the write-claim mechanism appears in both browser_snapshot and browser_handoff.

    Naming Consistency4/5

    All tools share a clean browser_ snake_case prefix, which makes the set predictable. Minor deviations exist in singular/plural noun usage (browser_group vs browser_groups) and several tools bundle multiple actions under one name (browser_group, browser_handoff, browser_tab).

    Tool Count5/5

    15 tools is well-scoped for a browser-control server covering access, observation, mutation, artifacts, human handoff and status. Each tool earns its place with no obvious redundancy.

    Completeness4/5

    The surface covers the full lifecycle: requesting access, listing tabs/groups, snapshotting, clicking/filling/typing/keying, screenshotting, handoff, and mutation-outcome recovery. Minor gaps like scroll, hover, and explicit select/dropdown manipulation could force workarounds, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow