bpc-oss/chrome-faithful

README excerpt

Chrome Faithful Faithful control of your real, logged-in Chrome profiles. An MCP server + MV3 Chrome extension + authenticated localhost bridge that lets AI agents drive the Chrome that already holds your logins, extensions, and history. No copied profiles, no debug profile, no --remote-debugging-port , no Edge, no global mouse/keyboard automation. English · 简体中文 Why this exists Browser-control tools optimize for different jobs: Approach What you get What you lose Chrome DevTools MCP (Google) Excellent DevTools, performance, and CDP workflows; Chrome 144+ can autoConnect to a running local browser with user approval Chrome must already be running, and when several profiles are active Chrome chooses the default profile rather than accepting an exact profile name Playwright / Puppeteer MCP servers Deterministic, isolated browsers that are ideal for CI and repeatable tests Existing logins, extensions, history, and two-factor sessions are not present unless separately provisioned Extension-based MCPs (BrowserMCP, real-browser-mcp) Control of an existing logged-in browser A strong fit for live sessions; multi-profile setups may require separate server instances and ports, and normally e…

Category