MCP-Undetected-Chromedriver
Related Servers
Alternatives to MCP-Undetected-Chromedriver
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server for stealth browser automation that uses human-like interaction patterns to bypass bot detection via the Chrome DevTools Protocol. It enables users to navigate, interact with elements, and capture data from websites using undetectable behaviors like Bezier mouse movements and Gaussian typing delays.121 npm1MIT
- AlicenseCqualityBmaintenanceMCP server for agent-piloted browser automation that clears Cloudflare, providing multi-session parallel Chromes, persistent profiles, stealth features, credential vault, and vision-first clicking.8646 PyPI7Apache 2.0
- AlicenseCqualityAmaintenanceMCP server for browser automation that drives Chrome via an extension, preserving login state and offering 45 tools for navigation, interaction, scraping, and screenshots.535MIT
- FlicenseCqualityDmaintenanceEnables browser automation, including navigation, form filling, login with CAPTCHA handling, and element manipulation, using a Chrome-based MCP server.364-
- AlicenseCqualityCmaintenanceProvides browser automation and web scraping as MCP tools, enabling autonomous URL ingestion, crawling, extraction, and anti-bot handling with interactive browser control.625MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.01MIT
TDQS
Scored across 16 tools
Most tools have distinct purposes targeting specific browser automation tasks like navigation, interaction, and content extraction. However, some overlap exists between browser_click and browser_iframe_click, where the latter is essentially a specialized version of the former for iframes, which could cause minor confusion.
All tools follow a consistent snake_case naming pattern with a clear 'browser_' prefix followed by a verb_noun structure (e.g., browser_click, browser_navigate, browser_screenshot). This uniformity makes the tool set predictable and easy to understand.
With 16 tools, the count is slightly high but reasonable for a browser automation server, covering a wide range of common web interaction tasks. It might feel a bit heavy, but each tool appears to serve a specific function without obvious redundancy.
The tool set provides comprehensive coverage for core browser automation, including navigation, clicking, typing, hovering, and content extraction. Minor gaps exist, such as no explicit tool for handling cookies, managing tabs, or waiting for elements, but agents can likely work around these using existing tools like browser_evalute or timeouts.