real-browser-mcp
Related Servers
Alternatives to real-browser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA local MCP server that enables AI coding assistants to drive the real, already-logged-in Chrome browser — navigating pages, clicking, typing, reading content, taking screenshots, and inspecting tabs, cookies, and network traffic through natural language. It works as a Chrome extension, so no remote-debugging port needs to be opened and pages the user is already signed into are fully usable.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive your real, already-logged-in Chrome — navigating, reading, clicking, filling forms, screenshotting, inspecting network traffic and cookies. Because it runs through a browser extension instead of a debugging port, it works on authenticated pages and passes bot detection without extra setup.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI assistants drive your real, already-logged-in Chrome through a browser extension, so agents can read, click, type, navigate, screenshot, inspect network traffic, and manage cookies or storage on pages that require existing sessions. It works without opening a remote-debugging port and keeps all communication on your machine.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding assistants drive the user's real, already-logged-in Chrome through a companion extension, with tools for navigation, snapshots, clicking, typing, reading page content, screenshots, tabs, network inspection, and cookies. It works without a remote-debugging port, so sessions and bot-detection state of the everyday browser are preserved while everything stays on the user's machine.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding assistants drive the Chrome browser you already have open, using your existing logged-in sessions. It enables navigating and reading pages, clicking, typing, filling forms, taking screenshots, uploading files, and inspecting console, network, storage, and cookies — without headless browsers or opening a remote-debugging port.1 npmISC
TDQS
Scored across 24 tools
Most tools map to a clearly distinct browser action, and descriptions do real work separating near-neighbors (browser_type vs browser_fill_form, browser_click vs browser_click_text vs browser_find). The main soft spots are browser_evaluate, browser_run_action, and browser_webmcp_execute_tool, which all execute code-ish things in the page and could be confused without careful reading.
Everything uses a uniform browser_ prefix followed by snake_case action words, so the set reads as one coherent namespace. The longer browser_webmcp_* names still follow the same pattern rather than breaking convention.
24 tools is on the heavy side, but browser automation genuinely needs this breadth (input, snapshots, dialogs, tabs, network, console, WebMCP). Each tool covers a real capability rather than duplicating another, though a few (click_text, find, run_action) could plausibly be folded into their general-purpose siblings.
The surface covers the full interaction lifecycle: navigate, observe (snapshot/text/screenshot/find), interact (click/type/select/hover/drag/upload), wait, and diagnose (console/network), plus tab management. Minor gaps remain around history navigation, cookies/storage, iframe or window targeting, and downloads.