A Claude Code plugin that drives your real, logged-in Chrome

[hamzahamidi]

chrome-devtools-mcp launches its own Chrome profile, so pages behind a login need a fresh sign-in. This came up in the Authenticated pages thread.

Claude Code takes a different route. claude --claude-in-chrome-mcp drives your real, logged-in Chrome through the Claude in Chrome extension. There is no separate profile or re-auth.

I packaged that bridge as a plugin:

/plugin marketplace add hamzahamidi/claude-in-chrome-cli
/plugin install claude-in-chrome@claude-in-chrome-cli

It registers the bridge as an MCP server, so the extension's tab tools show up natively in a session: navigate, read_page, find, form_input, computer, get_page_text, plus the console and network readers. It also ships a skill that tells the agent when a real session matters, and to work in its own tab group instead of the tabs you have open.

The repo also has cic.sh, the same bridge as a shell script, for cron, CI, or an agent that cannot keep an MCP connection open.

MIT, and the only requirements are the claude CLI and the extension: https://github.com/hamzahamidi/claude-in-chrome-cli

It only works if you are already running Claude Code, so it is not a replacement for this MCP. It is just a different tradeoff for the login problem people keep hitting here. Has anyone tried something similar with other extension-based bridges?