$ loading_
Give AI secure control of real logged-in Chrome profiles locally.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "chrome-faithful" yet — see the docs or source repo.
Use chrome-faithful and route to my "Work" Chrome profile. Open the target site and continue the task while keeping the existing logged-in session.
The AI performs web actions in the specified real Chrome profile without extra debug setup or re-login.
Use the "Personal" and "Test" Chrome profiles to visit the same website and record the differences in page state between them.
The AI routes accurately to different profiles and returns comparison results based on each profile's signed-in state.
Use chrome-faithful to run through a member-center workflow in my already logged-in Chrome profile and report whether each step is reachable.
The AI checks the workflow using a real signed-in session and outputs step-by-step validation results.
When developers or product managers need AI to operate signed-in websites directly, they can use it to connect to real local Chrome profiles. This avoids setting up separate debug browsers or temporary accounts for automation.
When the same site behaves differently across accounts, exact multi-profile routing lets AI enter each identity separately for inspection. This is useful for checking differences across personal, work, or test accounts.
For teams that care about local environment security, it connects to Chrome through a secure local bridge and extension instead of remote debugging ports. This fits use cases that want to reduce debugging exposure.
It is an MCP server that lets AI agents control real, logged-in Chrome profiles through a secure local bridge and extension. It focuses on faithfully connecting to existing browser environments with exact multi-profile routing.
According to the description, it does not use debug profiles or remote debugging ports. That means it targets real Chrome profiles rather than separate debug browser sessions.
The provided material only says it works through a local bridge and extension, but it does not include installation steps. For setup, runtime requirements, and configuration details, see the source repository.
Control Chrome via MCP for browsing, form filling, screenshots, and logs.
Control a real Chrome browser for browsing, interaction, and page reading.
Control Chrome with Playwright for end-to-end browser automation and iframe diagnostics.
Control Windows Chrome from WSL for low-overhead web automation and debugging.
Control Chrome and automate multi-session browsing through MCP clients.
Control Chrome locally or remotely to automate browsing, forms, screenshots, and scripts.