Independent open-source project / Initial public v0.1.0 / further QA pending
Visible Chrome Bridge
A Windows lifecycle wrapper that connects ChatGPT to an existing Chrome session through official MCP tooling.
I built Visible Chrome Bridge to make an existing Chrome session available to a personal ChatGPT MCP connection without creating a new browser profile, exposing an inbound debugging port or replacing the upstream tools.
- My role
- Independent developer and maintainer
- Technology
- PowerShell
- C#
- Node.js
- Chrome DevTools MCP
- Secure MCP Tunnel
- Windows
01 / The context
The problem
Connecting tools is only part of the problem. The local runtime also needs predictable startup and shutdown, safe handling of credentials, controlled dependencies and clear boundaries around the user’s browser.
02 / System thinking
How the pieces connect
Conceptual connection path. The bridge wraps official components; it is not a new MCP server or a Chrome automation engine.
- 01
ChatGPT
A tool call starts through the personal MCP connection.
- 02
Secure tunnel
The official client maintains an outbound connection.
- 03
Local runtime
The wrapper manages the tunnel and Chrome DevTools MCP processes.
- 04
Existing Chrome
The user enables remote debugging and approves access.
03 / Engineering
Decisions & trade-offs
01
Keep the browser outside the process tree
The bridge manages its own processes with a Windows Job Object, while leaving the user’s existing Chrome process alone.
Trade-off Browser availability and consent remain external conditions the wrapper cannot control.
02
Separate runtime credentials from the source
Local secrets use current-user Windows DPAPI and protected directories. The Chrome MCP child is not meant to inherit the tunnel runtime key.
Trade-off This reduces accidental exposure but does not protect against a compromised user session.
03
Pin and verify upstream dependencies
Installation verifies downloaded components, stages versions and provides manual update and rollback controls. Offline Windows tests exercise failure paths.
Trade-off Updates require deliberate review; verified downloads are not the same as an independent security audit.