Chrome for AI
Related Servers
Alternatives to Chrome for AI
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to control a stealth Patchright-driven browser via MCP, automating complex web tasks while evading anti-bot systems like Cloudflare, Akamai, Kasada, and DataDome.66563 npm1MIT
- AlicenseAqualityDmaintenanceStealth browser automation for AI agents, using source-patched Chromium to bypass bot detection systems like Cloudflare, reCAPTCHA, and FingerprintJS.28Apache 2.0
- FlicenseNot gradedqualityBmaintenanceProvides 29 stealth-browsing tools for AI agents, enabling undetected web automation and scraping through a patched Chromium engine.629-
- AlicenseAqualityAmaintenanceEnables AI agents to drive your real, logged-in Chrome browser with existing sessions and cookies, bypassing CAPTCHA and anti-bot measures, with support for multi-session and human-in-the-loop workflows.4046MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform real Google web searches and render web pages for content extraction using a local Chrome browser, with human-in-the-loop CAPTCHA verification, requiring no API keys.33 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform stealth browser automation and anti-detection web interaction, including session management, humanized interactions, and bypassing anti-bot/WAF protections.MIT
TDQS
Scored across 70 tools
Many tools have clear and distinct purposes (e.g., cookie, localStorage, sessionStorage groups), but there is overlap between browser_hover, browser_click, and browser_find for element interaction, and between browser_snapshot and browser_take_screenshot. The highlighted 'browser_video_show_actions' and 'browser_video_hide_actions' are specific to video recording, but there are many generic tools that could cause confusion in an agent.
The majority of tools follow a consistent 'browser_<verb>_<noun>' pattern (e.g., browser_cookie_list, browser_navigate). There are a few that break the pattern, such as 'stealth_status' and 'captcha_detect' which use a different prefix, and 'challenge_wait' and 'human_wait' which omit the 'browser_' prefix. However, these are a minority and the patterns within the browser_ prefix are well-maintained.
70 tools is a large number for a single MCP server. While the domain (browser automation and stealth) is broad, this count feels heavy and could be better scoped. Many tools cover niche or low-level operations (e.g., browser_mouse_down/up separately from browser_mouse_click_xy) that might be combined. The count brings the score to borderline high.
The tool set provides comprehensive coverage for browser automation, including navigation, interaction, storage, network, video, and stealth features. There are minor gaps, such as no explicit tool for managing browser history (only back) or for handling multiple tabs beyond 'browser_tabs', but the core workflows are well-covered and dead ends are rare.