Browser MCP
Related Servers
Alternatives to Browser MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLets AI assistants control your real Chrome browser to perform web tasks like reading pages, taking screenshots, clicking, and typing, using your existing logged-in sessions.133MIT
- AlicenseAqualityBmaintenanceEnables AI agents to access authenticated websites by reusing your existing browser profile and cookies, so you never share passwords and sessions persist between runs.55MIT
- AlicenseBqualityFmaintenanceEnables AI agents to directly control your real Chrome browser with full context including login sessions, cookies, and open tabs. It provides tools for page scanning, JavaScript execution, CDP control, screenshots, and physical mouse/keyboard input for authentic browser automation.20243MIT
- 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.4027 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to authenticate with websites using a real Chromium browser with anti-detection measures and human-in-the-loop support for captchas and 2FA. Features stealth browsing, human-like interactions, and persistent session storage to automate and resume login workflows.-
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to automate your existing browser using your logged-in profile. Provides fast, private browser automation that avoids bot detection by working with your real browser fingerprint.7,765 npmApache 2.0
TDQS
Scored across 40 tools
Most tools map cleanly to a distinct browser action, and the descriptions actively disambiguate close pairs like select_option/set_combobox, get_page_content/extract_list, and click/click_xy. The main fuzzy spots are browser_select_frame, whose name suggests frame selection but actually executes JavaScript, and the two meta feedback tools (browser_about vs browser_provide_feedback).
The browser_ prefix with mostly verb_noun names is consistent and predictable, e.g. list_tabs, close_tab, set_cookies, get_page_content. Minor deviations such as browser_about, browser_console_logs, browser_fetch, and the semantically mismatched browser_select_frame keep it from being a perfect 5.
At 40 tools this is well into the 25+ 'too many' range, and many of them are narrow fallback or recovery utilities (click_xy, drop_file, reattach_debugger, set_date, provide_feedback) that could be consolidated or documented as a smaller action set. The broad browser-automation domain makes the count understandable, but the surface is not well-scoped.
The toolkit covers the main browser lifecycle well: navigation, clicking/filling, waiting, tabs, frames, dialogs, storage/cookies, uploads, screenshots, and list extraction. Missing explicit back/forward/reload and general non-file drag-and-drop are minor gaps that can usually be worked around via browser_execute_script or browser_navigate.