seleniumbase-mcp
OfficialRelated Servers
Alternatives to seleniumbase-mcp
AlicenseAqualityAmaintenanceBrowser automation that bypasses anti-bot systems and handles web-scraping with CDP Mode.20024363,384 PyPI13,109MIT
Related Servers
- AlicenseAqualityDmaintenanceEnables undetected Chrome automation and JavaScript reverse engineering through SeleniumBase's CDP Mode, allowing MCP clients to control browsers and inspect page scripts.24MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to perform stealth browser automation with anti-detection, including navigation, clicking, typing, screenshots, and network monitoring via an MCP server.MIT
- AlicenseAqualityAmaintenanceEnables assistants such as Claude Code, Codex, and Gemini CLI to drive a real browser over MCP — navigating, clicking, typing, and reading live pages from plain-English instructions. Supports optional proxy routing, persistent profiles for surviving logins, and reproducible browser identities via seeds.121632,222MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to drive a real browser — navigating, clicking, typing, screenshotting, and inspecting pages through 30 MCP tools. Supports multi-step test scenarios, assertions, session recording, visual regression, and network/console monitoring, all from the terminal.106 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to drive a real browser through MCP, so it can navigate pages, click and type, capture screenshots and accessibility snapshots, run multi-step test scenarios with assertions, and monitor console and network activity.106 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to control a real browser for navigating, clicking, typing, taking screenshots, inspecting pages, and running multi-step automated tests. It also supports visual regression, session recording, and network/console monitoring through MCP tools.106 npmMIT
TDQS
Scored across 24 tools
Most tools have clearly distinct purposes (click_element vs type_text vs select_option vs hover_action), and the descriptions include explicit 'Tool selection' guidance to disambiguate overlapping read/check/wait/assert tools. However, check_if_condition, wait_for_condition, and assert_condition form a closely related trio that could still cause misselection despite the guidance.
Tool names mostly follow a consistent verb_noun pattern (start_browser, close_browser, click_element, type_text, find_elements, get_content, manage_cookies, manage_tabs, manage_window, manage_history, manage_storage, scroll_page, save_page, open_url, hover_action, select_option, focus_element, run_javascript, solve_captcha). Minor deviations: check_if_condition, wait_for_condition, and assert_condition use a different 'condition' suffix pattern, and get_page_info breaks the get_* noun pattern slightly.
24 tools is on the higher end but appropriate for a full browser automation server covering lifecycle, navigation, element interaction, state inspection, storage, tabs, windows, and page saving. The count is justified by the breadth of the domain, though it is close to the threshold where it starts feeling heavy.
The tool surface covers the full browser automation lifecycle: browser start/close, navigation, history, tabs, windows, element finding/clicking/typing/selecting/hovering/focusing, content reading, attribute reading, condition checking/waiting/asserting, cookies, storage, JavaScript execution, captcha solving, and page saving. No obvious dead ends or missing core operations for the stated purpose.