Jev Browser Bridge
Related Servers
Alternatives to Jev Browser Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables remote agents to control a local Chrome/Edge browser via MCP, supporting navigation, snapshots, clicks, typing, screenshots, and script execution.8 npmISC
- 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-
- AlicenseNot gradedqualityDmaintenanceEnables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.497 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.2 npmMIT
- AlicenseBqualityBmaintenanceEnables MCP clients to drive the Chrome or Edge tabs you already have open and signed in, by pairing with a local browser extension instead of launching a remote debugging port or a separate automation browser. Exposes 20 tools for accessibility-tree snapshots, clicking and filling, navigation, uploads, screenshots, JavaScript evaluation, and console and network log reading.246,478 npm4MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP agents to drive the user's already-open Chrome profile through a Manifest V3 extension and loopback bridge, listing and controlling existing tabs, capturing screenshots, and sending clicks, typing, drags and key holds via an independent on-page cursor without moving the system mouse. It also supports form filling, console and network inspection, read-only or confirmed JavaScript execution, file and PDF downloads, and game-style screenshot/action loops with snapshot recovery and an emergency stop.MIT
TDQS
Scored across 23 tools
Tools are largely distinct, with clear prefixes and domain-specific actions. Minor overlap exists between browser_type (focused element) and browser_fill (selector-based), and between browser_goto and browser_http_get, but descriptions mostly disambiguate them.
All tools share the browser_ prefix and lowercase snake_case, creating a predictable style. A few names are noun-like rather than verb-first (browser_page_info, browser_current_tab, browser_js, browser_cdp), so it is not perfectly uniform.
23 tools is on the heavier side and crosses into 'feels heavy' territory, though most operations are legitimate browser actions. The wait variants and raw CDP/JS escape hatches add some redundancy, making the set slightly larger than ideal.
The set covers core browser automation workflows: navigation, tabs, input, waiting, screenshots, uploads, recording, JS evaluation, and raw CDP. Missing conveniences like back/forward/reload and more advanced DOM inspection can be worked around via browser_js or browser_cdp.