Chrome Bridge

Connect Chrome tabs to the local chrome-bridge MCP server.

Chrome Bridge connects the Chrome browser you already use to a local Model Context Protocol (MCP) server. An MCP client can list and select tabs, capture accessibility snapshots, and perform explicit page operations without automatically bringing a background target to the foreground. Data disclosure: Chrome Bridge can read and interact with HTTP and HTTPS pages when instructed by the user's MCP client. Page information and operation results are sent to the WebSocket endpoint configured by the user, which defaults to the Chrome Bridge server on the same machine. The Chrome Bridge project does not operate a server that receives this data. Main features: - Operate tabs across Chrome windows and multiple profiles with explicit routing. - Select a background target independently from Chrome's active tab. - Use generation-scoped accessibility references for click, type, select, drag, and file-upload operations. - Capture viewport screenshots and current-document console messages. - Record explicitly requested operations as silent WebM files saved locally below Downloads/chrome-bridge. - Connect to a user-configured WebSocket endpoint; the supported default is the local Chrome Bridge MCP server on 127.0.0.1. Chrome Bridge requires the separate chrome-bridge-mcp local server and an MCP-compatible client. It does not provide a cloud relay, analytics, or advertising.