Chrome Bridge
Related Servers
Alternatives to Chrome Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to drive a real Chrome instance over the Chrome DevTools Protocol — opening and navigating tabs, reading compact YAML page outlines with refs, clicking, typing, scrolling, screenshotting, and evaluating scripts — with no browser extension or installed dependencies. It also audits pages for horizontal overflow and WCAG AA contrast, available both as an MCP tool and as a CI-friendly CLI.6 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's real, already-logged-in Chrome — reading pages, clicking, typing, uploading files, taking screenshots, and inspecting tabs, cookies, console, and network traffic — via 25 browser automation tools that pass bot detection without a debugging port. Requires a companion Chrome extension and stays entirely on the user's machine.1 npmISC
- AlicenseBqualityBmaintenanceTurns Chrome into a local MCP server, giving AI agents 51 browser tools to inspect DOM, automate clicks, run JavaScript, audit security and accessibility, mock APIs, extract data, record demos, and more from any MCP client.92615 npmMIT
- 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 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
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's own already-logged-in Chrome, reading pages, clicking, typing, filling forms, taking screenshots, and inspecting storage, network, and console state. It works through a Chrome extension rather than a remote-debugging port, so no data leaves the machine and bot detection is bypassed.1 npmISC
TDQS
Scored across 69 tools
The descriptions are exhaustively cross-referenced, which helps, but the 69-tool set still has genuinely crowded areas: four screenshot variants, four read paths (read_page, extract, extract_table, query_dom, find_text), and monitor_network vs network_rules vs track_events vs read_console all need careful reading to separate. An agent can usually pick right thanks to the 'use X instead' notes, but the boundaries are not self-evident from names alone.
Most tools follow snake_case verb_noun (get_tabs, create_tab, set_storage, full_page_screenshot), but there is a large minority of bare verbs and noun-only names (navigate, extract, click, hover, scroll, assert, watch, audit, handoff, clipboard, animations, frames, lighthouse). The convention is readable but only loosely followed.
69 tools is far beyond a comfortable set for an agent, and the existence of an opt-in 'caps' mechanism (audits, visual, perf, network, storage, dom, files) confirms the surface was split because it is too large. Splitting into cap groups is the right mitigation, but as a flat tool list it is heavy.
Coverage is exceptionally thorough for a browser bridge: navigation, tabs/windows, DOM read/write, forms, dialogs, storage, network interception, performance/audit, screenshots, downloads, WebMCP, and human handoff. Almost no plausible browser-automation operation is missing.