Control authenticated Chrome sessions through MCP with OpenChrome
Let an agent drive a real logged-in Chrome profile through MCP for authenticated browsing, parallel tab work, and token-efficient page interaction without re-authenticating each run.
Prerequisites
Node.js, npm, Google Chrome, MCP-compatible client
Installation
Use the upstream install or setup path that matches your environment:
- npm install -g openchrome-mcp
- npx openchrome-mcp setup --client opencode # OpenCode
Requirements and caveats from upstream:
- (macOS / Windows / Linux, beta) runs the server with no Node.js setup.
- launched it (Docker, systemd, CI):
- openchrome doctor # Node, disk, Chrome binary/port, orphans, perms, locks
Basic usage or getting-started notes:
-
bash
-
openchrome setup # Claude Code
-
openchrome setup --client codex # Codex CLI
-
Extracted from upstream docs: https://raw.githubusercontent.com/shaun0927/openchrome/HEAD/README.md