browsermcp-plus
Related Servers
Alternatives to browsermcp-plus
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn MCP server that provides AI models with full browser automation capabilities through Chrome. It enables navigation, interaction, screenshots, and complete DevTools access by bridging AI clients with a companion Chrome extension.9912 npm3Apache 2.0
- FlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents mouse-and-keyboard control over a live Chrome session, enabling navigation, clicking, typing, screenshots, and DOM inspection.14 npm-
- AlicenseNot gradedqualityNot gradedmaintenanceAn extension-based MCP server that enables AI assistants to control your existing Chrome browser, leveraging your active login states and settings for automation. It provides over 20 tools for tasks like semantic tab search, screen capture, network monitoring, and direct element interaction.-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives AI agents faithful control of real, logged-in Chrome profiles via a secure local bridge and extension, with exact multi-profile routing and no debug profiles or remote debugging ports.5MIT
- AlicenseNot gradedqualityDmaintenanceAn extension-based MCP server that enables AI assistants to control your browser, leveraging existing sessions and login states for automation and content analysis. It provides over 20 tools for semantic tab search, interactive element manipulation, and network monitoring directly within your daily Chrome environment.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI assistants with full control over a real browser session via a Chrome extension, supporting 36 tools for navigation, data extraction, and DOM manipulation. It bypasses bot detection by utilizing the user's active browser session, including cookies, authentication tokens, and installed extensions.14 npm3MIT
TDQS
Scored across 25 tools
Most tools map to clearly distinct browser actions (navigation, interaction, tabs, waiting, inspection) with little overlap. Pairs like browser_type vs browser_fill_form and browser_wait vs browser_wait_for are differentiated by their descriptions, but the high tool count creates minor potential for confusion.
All 25 tools use a consistent browser_ prefix and snake_case, following a predictable verb or noun pattern (e.g., browser_navigate, browser_tab_close, browser_get_console_logs). No mixed conventions are present.
25 tools is on the heavy side for a browser automation server. While each tool has a purpose, several could be consolidated (e.g., wait/wait_for, type/fill_form), placing the count in the borderline-heavy range per the rubric.
The surface covers core browser lifecycle actions: navigation, tab management, interaction, waiting, screenshots, console logs, JS evaluation, and dialog handling. Minor gaps like direct URL/title access or network/cookie management exist but are workaroundable via browser_evaluate.