Skip to main content
Glama
Sign In
1password-browser-mcp

1password-browser-mcp

by marekkirejczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to 1password-browser-mcp

No user-submitted related servers found.

    Related Servers

    • better-browser-mcp

      alexsorokoletov
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives any MCP-compatible AI agent control of the user's own Chrome profile with existing sign-ins, returning compact text snapshots and batched action results so browsing tasks finish in far fewer calls and tokens. Includes safety guards against unwanted purchases or posts, prompt-injection flagging, and isolated agent tab groups that never steal the user's focus.
      13 npm
      2
      MIT

    • MultiZen

      Helen25865
      F
      license
      Not graded
      quality
      A
      maintenance
      Lets any MCP client drive isolated local Chromium or Firefox profiles — navigating, clicking, typing, extracting content, taking screenshots, evaluating JS, and managing tabs and cookies — each with its own spoofed fingerprint, proxy, and locale. Per-profile cookies and login state persist across launches, so agents can complete real authenticated workflows.
      -

    • huahaimaker-chrome

      huahaimaker
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-capable AI agent to operate the user's own everyday Chrome browser with all existing login sessions intact, offering 22 tools for reading page/network data, filling forms, clicking, batch multi-step actions, and handing CAPTCHAs or confirmations back to the human — without API keys, debug ports, or launch flags.
      MIT

    • MultiZen

      lukasharrison03
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive isolated local browser profiles, each with its own persistent cookies, login state, fingerprint, and proxy, so authenticated workflows carry across sessions. Exposes tools for navigation, clicking, typing, extraction, screenshots, JS evaluation, tab and cookie management, and raw CDP commands to any MCP client.
      MIT

    • huashu-chrome

      alchaincyf
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-compatible AI agent to drive your own Chrome browser with your existing login state, filling forms, clicking elements, fetching data, and handling captchas without API keys or re-authentication.
      1,119 npm
      587
      MIT

    • MultiZen

      brahimf3305
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a localhost MCP endpoint that lets AI agents drive isolated browser profiles — navigating, clicking, typing, extracting, screenshotting, evaluating JS, and managing tabs and cookies — so real authenticated workflows can be completed from MCP clients like Cursor or Claude Desktop. Cookies, login state, fingerprints, and proxies persist per profile across launches and AI sessions.
      -
    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.2/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target distinct browser actions, and the browser_ vs onepassword_ prefixes make the domain split clear. There is some overlap among reading tools (snapshot, find, get_text) and between type/fill_form, but descriptions generally guide selection.

    Naming Consistency5/5

    All tools use consistent snake_case with predictable browser_ and onepassword_ prefixes followed by clear action/resource names. Multi-action tools like browser_tabs and browser_history are still readable and consistent.

    Tool Count3/5

    At 27 tools the surface is heavy, though browser automation naturally requires many granular actions. A few operations could potentially be consolidated, but most tools earn their place, making this borderline rather than clearly excessive.

    Completeness4/5

    The server covers a broad browser automation lifecycle: navigation, inspection, interaction, dialogs, uploads, JS evaluation, console/network, and 1Password fill/OTP/items/status. Minor gaps like drag-and-drop, download handling, or credential save/update prevent a perfect completeness score.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources