seleniumbase-mcp
Related Servers
Alternatives to seleniumbase-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables MCP clients like Claude Desktop and Claude Code to drive a real browser with SeleniumBase automation. Offers three variants: WebDriver-based general automation, Pure CDP Mode for bot-detection bypass, and a broad SB() API with MFA and downloads.1222457 PyPI9MIT- AlicenseAqualityAmaintenanceEnables direct browser control via Chrome DevTools Protocol, supporting navigation, interaction, content extraction, and screenshots through a single MCP tool.1355MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.AGPL 3.0
- AlicenseAqualityAmaintenanceControls a running Chrome/Chromium browser via the Chrome DevTools Protocol, enabling navigation, JavaScript evaluation, tab management, and raw CDP commands through MCP tools.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to control and inspect a live Chrome browser via MCP, including performance tracing, network and console debugging, screenshots, and reliable Puppeteer-based automation.2,487,841 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.107 npmMIT
TDQS
Scored across 24 tools
Tools are organized into clear functional groups (lifecycle, navigation, reading, interaction, synchronization, browser state), and each includes explicit tool-selection guidance. The only real ambiguity is among the condition tools and between get_content/find_elements, but the descriptions resolve those boundaries.
Almost all tools use a predictable verb_object snake_case pattern such as click_element, type_text, and manage_cookies. Minor deviations like hover_action and check_if_condition introduce slight inconsistency, but the overall convention is clear and consistent.
24 tools puts this server in the heavy range, above the typical 3-15 sweet spot. The count is not bloated because each tool maps to a distinct browser capability, but it is borderline and will require careful tool selection.
The surface covers the full browser workflow: session lifecycle, navigation/history/tabs, element reads and interactions, synchronization/assertions, cookies/storage, page output, and a JavaScript escape hatch. Minor gaps such as explicit keyboard input, file upload, or alert handling remain, but they can be worked around for most workflows.