Skip to main content
Glama
Sign In
duplex

duplex

by Eric-huang799
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to duplex

No user-submitted related servers found.

    Related Servers

    • PolterTab

      abhinav162
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server paired with a Chrome extension that lets any MCP-compatible AI agent drive the browser you're already signed into — navigating, clicking, filling forms, scraping and extracting structured records using your real profile, cookies and logged-in sessions. It exposes 28 browser_* tools over stdio and relays them to the extension on localhost, with capabilities like paginated record extraction, ref-tagged snapshots, screenshots, and opt-in file uploads.
      538 npm
      1
      ISC

    • Orvima

      Sachitt-AV-08
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-capable AI client to drive the user's own Chrome or Edge browser through a set of browse_* tools — navigating, clicking, typing, extracting, and managing tabs with their existing logins on their own machine. Runs locally and self-hosted with a live viewport and pause/approve controls so every verified step stays under user watch.
      4
      MIT
    • lyra-browser

      lyra-browserofficial

      Intrect-io
      A
      license
      B
      quality
      B
      maintenance
      Exposes a headful, collaborative browser over MCP so an agent and a user can share one visible Chromium window: the agent navigates, reads, clicks, types, and fills forms, while the user watches and can take over for passwords, CAPTCHAs, 2FA, and payments, with every action written to an append-only audit trail. It also runs headless under a chat-based harness.
      29
      225 PyPI
      MIT

    • byob

      Jasonz68342
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding tools to drive the user's real, already-logged-in Chrome through an MCP stdio interface, exposing 25 tools for navigating, clicking, typing, reading pages, taking screenshots, capturing network traffic, and accessing cookies and storage. The bundled Chrome extension talks to a local bridge instead of an open remote-debugging port, so logged-in sessions and bot-detection-proof human browsing work without extra setup.
      1 npm
      ISC

    • 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

    • byob

      timothynowak98572
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the user's real, already-logged-in Chrome — reading pages, clicking, typing, uploading files, taking screenshots, and inspecting tabs, cookies, console, and network traffic — via 25 browser automation tools that pass bot detection without a debugging port. Requires a companion Chrome extension and stays entirely on the user's machine.
      1 npm
      ISC
    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 24 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: tab management, navigation, interaction, and inspection are well separated. There is some overlap among page-inspection tools (snapshot, get_html, query, screenshot, evaluate), but the descriptions clarify when to use each.

    Naming Consistency3/5

    The naming mixes verb-style tools (click, type, navigate, scroll) with noun-style tools (history, snapshot, screenshot, query, evaluate). Some compound names follow verb_noun (new_tab, list_tabs, close_tab, get_html), but the overall convention is inconsistent.

    Tool Count3/5

    At 24 tools this is heavy for a single server, even for browser automation. Most tools are meaningful, but the surface is near the upper bound of what an agent can comfortably reason over without confusion.

    Completeness4/5

    The toolset covers navigation, tab lifecycle, page inspection, interaction, file upload, waiting, console access, search, and JS evaluation. Minor gaps remain around dialog handling, cookies/storage, and network interception, but core browser workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Resources