A
licenseA
qualityD
maintenanceAutomate your browser with AI using your existing profile, enabling logged-in sessions and stealth automation.
12
36,790 npm
Apache 2.0
Superior Browser MCP
Related Servers
Alternatives to Superior Browser MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to perform intelligent browser automation with session-based context analysis, including navigation, form filling, and content extraction through natural language.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to drive a real browser with human-like pointer and keyboard actions for navigation, form interaction, and page reading. It supports stealth-oriented browsing with optional proxy, persistent profile, and seeded identity settings.16MIT
- AlicenseAqualityDmaintenanceEnables browser automation with anti-detection features, including navigation, interaction, form filling, and session management.2244 PyPI10MIT
- AlicenseAqualityCmaintenanceEnables AI agents to fully control a browser for web automation, including navigation, clicking, typing, scrolling, screenshots, and DOM inspection, with session persistence and anti-bot bypass.4012 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to navigate, interact with, search, extract from, download from, and reuse sessions across the web using anti-detection browser automation.971 npmMIT
TDQS
C2.6/5.0
Scored across 42 tools
Disambiguation2/5
Many tools have overlapping purposes, such as browser_interact vs click_by_overlay_id/hover_by_overlay_id, browser_fill_form vs smart_fill_form, and several detection tools (popups, ads, captcha, login). The visual/interactive map tools also overlap heavily. Agents will struggle to choose the right tool.
Naming Consistency1/5
Tool names mix snake_case (click_by_overlay_id, detect_popups) with camelCase (browser_navigate, browser_take_screenshot), and some use the 'browser_' prefix while others do not. There is no consistent verb_noun pattern, making the API feel chaotic.
Tool Count2/5
42 tools is excessive for a browser automation server, especially when many could be consolidated (e.g., unified interaction tool, unified form tool, unified detection tool). The high count with redundancy suggests the set is not well-scoped.
Completeness4/5
The server covers a wide range of browser automation needs: navigation, interaction, forms, screenshots, popups, ads, captchas, cookies, storage, network, console, performance, tabs, windows, dialogs, and extensions. Minor gaps exist (e.g., explicit element selection or file upload tool, though browser_interact covers them), but overall the surface is quite comprehensive.
Maintenance
ActivityInactive
ResponsivenessNo issues