arc-control-mcp
Related Servers
Alternatives to arc-control-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables inspection and control of Arc Browser spaces and tabs on macOS, including reading sidebar/history data and performing actions like focusing spaces, creating and closing tabs.131MIT
- FlicenseNot gradedqualityCmaintenanceEnables semantic browser automation for the Arc browser, allowing users to perform web tasks like searching, shopping, and data extraction through natural language commands.1-
- AlicenseNot gradedqualityAmaintenanceEnables local AI agents to operate the user's existing browser session via a Manifest V3 extension and native messaging, supporting tabs, DOM snapshots, clicks, form input, JavaScript, screenshots, cookies, network capture, and Arc Spaces.42 npmMIT
- AlicenseAqualityDmaintenanceEnables macOS system automation, window management, and productivity tools for AI agents, including running AppleScripts, opening apps, retrieving browser tabs, taking screenshots, and controlling system settings.21MIT
- AlicenseAqualityCmaintenanceEnables Claude Code to control the Arc browser over CDP, including navigation, clicking, form filling, screenshots, and reading console and network traffic.11MIT
- FlicenseNot gradedqualityBmaintenanceLets AI agents drive your real, already-logged-in browsers on macOS in the background without stealing focus, organizing work into tab groups, reading pages as compact accessibility snapshots, and saving repeatable scenarios. Supports Chrome, Edge, Brave, Yandex Browser, and Safari, with per-agent isolation and automatic tab cleanup.-
TDQS
Scored across 50 tools
The set includes many overlapping alternatives: synthetic vs trusted clicks, fill vs type vs trusted_type, press_key vs trusted_press_key, hover vs trusted_hover, and several wait/capture/network tools. Descriptions are unusually detailed and explicitly distinguish use cases, but the sheer number of similar action tools still creates meaningful misselection risk.
Names consistently use snake_case with clear action or resource orientation, and the trusted_ prefix is applied predictably. There is no camelCase/snake_case mixing, and even single-word tools like click, fill, and scroll fit the domain vocabulary.
At 50 tools, the surface is far above the typical 3-15 well-scoped range and well into the too-many category. Although Arc browser control is a broad domain, many tools duplicate capabilities or differ only by synthetic/trusted/CDP execution path, so consolidation would be feasible.
Coverage is broad: tab lifecycle, navigation, page inspection, interaction, CDP, screenshots, dialogs, capture, history, archive, spaces, and stale-tab cleanup are all represented. Minor gaps remain around mutating Arc-specific organization, such as moving tabs between spaces, managing pinned tabs/folders, or restoring archived tabs.