PhantomHand
Related Servers
Alternatives to PhantomHand
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceA lightweight 30KB MCP browser automation server that uses raw Chrome DevTools Protocol to enable AI agents to browse the web, take screenshots, interact with elements, and capture live page events like console logs and network requests.26220 npm16MIT
- AlicenseNot gradedqualityCmaintenanceThe Zero-Setup Local Browser MCP. Enables AI agents to control web browsers via CDP with zero vision tokens and high-speed DOM mapping.17 npmMIT
- FlicenseNot gradedqualityBmaintenanceUniversal MCP server that enables any LLM agent (Claude, Cursor, Cline) to control a real Chrome browser with 5 perception engines, resilient heartbeat, and real-time vision streaming.-
- FlicenseBqualityCmaintenanceUltra-fast browser automation server over Chrome DevTools Protocol (CDP), exposed as MCP, enabling AI agents to control a real Chrome browser with low latency and minimal token usage.212-
- 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 gradedqualityAmaintenanceAn MCP server that lets LLM agents control all Chrome browser tabs via accessibility snapshots, element references, and a virtual cursor, supporting operations like click, type, navigate, screenshot, and video recording.MIT
TDQS
Scored across 41 tools
Each browser automation tool has a clearly distinct purpose, with different click types, input methods, and navigation actions that are well-described and non-overlapping. Even similar actions like browser_type and browser_set_value are differentiated by how they interact with elements.
Almost all tools follow the consistent pattern of 'browser_' prefix with snake_case verb_noun names (e.g., browser_click, browser_navigate). The only exception is 'get_extension_info' which lacks the prefix, breaking the pattern slightly.
With 41 tools, the server covers a very broad scope of browser interactions. While each tool is justified, the count is on the high end and could potentially be reduced by combining some related actions into more parameterized tools.
The tool set covers nearly all common browser automation scenarios including navigation, clicking, typing, scrolling, tab management, clipboard, sessions, and file operations. A minor gap is the lack of a tool for extracting structured page data beyond raw text/HTML.