agent-browser-mcp
Related Servers
Alternatives to agent-browser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.1Apache 2.0
- AlicenseAqualityAmaintenanceMCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.251Apache 2.0

browser-relayofficial
AlicenseNot gradedqualityCmaintenanceMCP server that drives a user's real Chrome browser via a WebSocket-connected MV3 extension, enabling tab management, navigation, page interaction, screenshots, and script evaluation through natural language.5 npmMIT- FlicenseNot gradedqualityDmaintenanceDrive your real, signed-in Chrome browser from any MCP client, enabling browser automation such as navigation, clicking, typing, and screenshots through standard MCP tools.1-
- FlicenseAqualityBmaintenanceAn MCP server that enables remote observation and control of a Chromium browser via a WebSocket relay, supporting DOM, CDP, and native OS automation for local or LAN-based AI agents.8-
- AlicenseNot gradedqualityDmaintenanceMCP server to control Chrome browsers locally or remotely via the Claude extension, enabling navigation, form filling, screenshots, and JavaScript execution from any MCP client.MIT
TDQS
Scored across 51 tools
Most tools target distinct capabilities (tab management, page input, cookies, storage, capture, CDP), and long descriptions clarify edge cases. Minor overlap exists between handle_dialog and resolve_leave_dialog, and between list_tabs/list_all_tabs/debugger_targets, but the descriptions draw clear boundaries.
The overwhelming majority follow a verb_noun snake_case pattern (open_url, list_tabs, delete_cookies, capture_page_screenshot), with parallel pairs like network_capture_start/network_capture_stop. A few noun-led names (extension_path, debugger_targets, cdp_command, cdp_batch, debugger_targets, cdp_batch) deviate slightly but remain predictable.
51 tools is well beyond the 25+ threshold and near the 50+ extreme, making the surface heavy for agents to navigate. The breadth is partly justified by the server's wide browser-automation scope, but many niche tools (extension management, native file dialogs, bookmarks) inflate the count.
The server covers nearly the full browser lifecycle: tabs, navigation, input, screenshots, cookies, storage, uploads, downloads, dialogs, permissions, network/console capture, and diagnostics, with no major dead ends in core workflows. Minor gaps like bookmark update and extension install are absent or explicitly unsupported, but workarounds exist via execute_js/cdp_command.