nodriver-mcp-server
Related Servers
Alternatives to nodriver-mcp-server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceUndetectable browser automation server for MCP-compatible AI agents, offering 225 tools across 32 sections to navigate, extract, clone pages, and bypass antibot systems like Cloudflare.1-
- AlicenseNot gradedqualityDmaintenanceA stealth-enhanced browser automation MCP server for AI agents to interact with websites while bypassing anti-bot detection mechanisms like Cloudflare and reCAPTCHA.9MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI assistants with full control over a real browser session via a Chrome extension, supporting 36 tools for navigation, data extraction, and DOM manipulation. It bypasses bot detection by utilizing the user's active browser session, including cookies, authentication tokens, and installed extensions.16 npm3MIT
- AlicenseAqualityFmaintenanceAn MCP server that provides LLMs with stealth browser automation capabilities via CloakBrowser to bypass bot detection services like Cloudflare and reCAPTCHA. It supports full page interaction, content extraction, and human-like behavior through 30 specialized tools.2052 PyPI13Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides an undetectable Playwright browser to bypass Cloudflare and other bot detection systems, enabling AI agents to navigate and scrape web pages without being blocked.11 npmMIT
- AlicenseNot gradedqualityDmaintenanceStealth Chrome MCP server for AI agents providing 77 tools, perfect bot detection scores, proxy pools, encrypted sessions, and live human handoff via Cloudflare tunnel.MIT
TDQS
Scored across 70 tools
Every tool targets a distinct action and resource, with descriptions that explicitly cross-reference alternatives (e.g., fill vs type_text vs press_key; take_snapshot vs get_page_content). Even subtle pairs like close_browser vs shutdown_browser are carefully delineated. There is little risk of an agent misselecting a tool.
The overwhelming majority follow a verb_noun snake_case pattern (list_pages, create_profile, set_cookie). Minor deviations exist: cf_verify uses an abbreviation+verb, performance_start_trace inverts the verb position, and a few bare verbs (fill, click, hover, drag) stand alone. These are readable but break the strict pattern.
70 tools is far beyond the typical well-scoped server and makes selection expensive for an agent. Although the domain of browser automation is broad, many niche features (audit_security, capture_bodies, inspect_storage, manage_extensions) could be separate services or consolidated. The count feels heavy rather than lean.
The surface covers the full browser automation lifecycle: pages, navigation, interaction, waiting, scrolling, forms, frames, dialogs, network, performance, storage, sessions, profiles, emulation, and browser configuration. There are no dead ends; the only conceivable gaps (e.g., download handling) can be worked around with evaluate_script or other existing tools. This is one of the most complete tool sets imaginable for its domain.