duplex
Related Servers
Alternatives to duplex
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.19 npmMIT
- FlicenseAqualityBmaintenanceLets 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-
- AlicenseNot gradedqualityAmaintenancesingle-binary MCP server that gives AI agents a browser. 66 tools for navigation, form filling, data extraction, screenshots, and DOM diffing — built on pure Chrome DevTools Protocol.13MIT
- AlicenseNot gradedqualityAmaintenanceA zero-dependency MCP server that drives a real Chrome browser through a companion extension, enabling AI agents to automate real user sessions with trusted input events, compact accessibility-tree snapshots, and 14 tools for navigation, interaction, scripting, and inspection.280 npmMIT
- AlicenseAqualityAmaintenanceMCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.251Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA native MCP server that gives AI assistants full Chrome control via the DevTools Protocol and an unpacked extension, including semantic element refs, real input, screenshots, and browser/tab/window management. It exposes 43 callable tools with a visible control overlay and an optional read-only security profile.2MIT
TDQS
Scored across 24 tools
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.
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.
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.
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.