Skip to main content
Glama
Eric-huang799

duplex

by Eric-huang799
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to duplex

No user-submitted related servers found.

    Related Servers

    • Orvima

      Sachitt-AV-08
      A
      license
      Not graded
      quality
      A
      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.
      3
      MIT
    • lyra-browser by Intrect-io

      lyra-browserofficial

      Intrect-io
      A
      license
      B
      quality
      C
      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
      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

    • page-bridge

      fannis9
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI agent to read and operate the Chrome or Edge tabs you are already using — titles, URLs, text, HTML, screenshots, clicks, typing, scrolling, and tab management — via a browser extension and native messaging, without restarting the browser, switching profiles, or opening a debug port. It exposes these capabilities as 19 MCP tools, with access limited to explicitly shared tabs and hardened by per-tab, origin-bound grants plus domain allow/deny lists.
      1
      MIT

    • Pagewright (browser-mcp)

      zamansheikh
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control the user's real Chrome/Brave/Edge profile over MCP, so they can read pages, click, type, take screenshots, audit layouts, debug CSS, and scrape paginated or infinite-scroll data. Because it drives the normal browser via the DevTools protocol with real input events, it works on modern JavaScript apps and on sites where the user is logged in.
      12 npm
      1
      MIT

    • aiwebhelper

      unilab-hq
      F
      license
      A
      quality
      B
      maintenance
      Lets an AI share the same live browser tab as a person, receiving the user's Alt+click target and enabling the AI to inspect, click, fill, type, navigate, or otherwise operate on that real page. It runs locally and pairs with the browser extension to bridge the user's page to the MCP client.
      13
      -
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Tools largely have distinct purposes, but page inspection tools (snapshot, get_html, query, screenshot) overlap in their goal of revealing page content, which could occasionally cause an agent to pick a less efficient method. Interaction tools (click, dblclick, hover, drag) are well separated, and navigation/tab management tools are clearly distinct.

    Naming Consistency3/5

    All names use snake_case, but the verb/noun pattern is inconsistent: some are verb_noun (list_tabs, get_html, select_option), while many are single verbs (navigate, click, type) or nouns (history, snapshot, screenshot). It remains readable, but the convention is mixed.

    Tool Count3/5

    With 24 tools, the set feels heavy for a browser automation server. Most tools are useful, but the count lands in the borderline-heavy range (16-25) where consolidation or clearer grouping could improve usability.

    Completeness4/5

    The surface covers core browser automation needs: tab management, navigation, page inspection, user interactions, waits, console reading, search, and even human annotation and JavaScript evaluation. Minor gaps exist around cookies/storage, dialogs, and frame handling, but these can often be worked around with evaluate.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources