seleniumbase-mcp
OfficialRelated Servers
Alternatives to seleniumbase-mcp
AlicenseAqualityAmaintenanceBrowser automation that bypasses anti-bot systems and handles web-scraping with CDP Mode.4912413,007MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables undetected Chrome automation and JavaScript reverse engineering through SeleniumBase's CDP Mode, allowing MCP clients to control browsers and inspect page scripts.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to perform stealth browser automation with anti-detection, including navigation, clicking, typing, screenshots, and network monitoring via an MCP server.MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude Code to control a real browser using AI for web scraping, competitive intelligence, and UX auditing through the MCP protocol.-
- AlicenseNot gradedqualityDmaintenanceEnables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.1MIT
- AlicenseBqualityCmaintenanceProvides undetectable browser automation for LLM agents via MCP, enabling real Chrome interaction with stealth features, DOM accessibility, and DevTools integration.983MIT
- AlicenseNot gradedqualityDmaintenanceEnables browser automation through MCP clients like Claude or Cursor, using the client's existing LLM without requiring an additional API key.Apache 2.0
TDQS
Scored across 24 tools
Each tool targets a clearly distinct browser operation, and descriptions include explicit 'Tool selection' guidance that resolves potential overlaps (e.g., check_condition vs wait_for vs assert_condition, get_content vs find_elements vs get_page_info). The few ambiguous pairs like scroll vs focus(action='scroll_to_element') are explicitly differentiated in the descriptions.
The tool set uses consistent snake_case throughout, but several tools are single verbs (navigate, click, focus, scroll) while most others follow a verb_noun pattern (start_browser, get_content, manage_cookies). This minor deviation is still readable and predictable overall.
24 tools is at the upper end and feels heavy for a single browser-automation server, even though most tools serve distinct purposes. The surface is comprehensive and well-organized, but it borders on over-provisioned for the stated scope.
The server covers browser lifecycle, navigation, content inspection, interaction, cookies/storage, windows/tabs, waits/assertions, CAPTCHA, and JavaScript fallback, which is a broad and coherent surface. Minor gaps include explicit alert/dialog handling, file upload, and full iframe switching, though some of these can be worked around via run_javascript or scoped click.