Chromeflow
Let Claude Code or Codex CLI control your logged-in Chrome for real UI checks, flows, and demos without rebuilding auth in headless browsers.
Overview
Chromeflow is a MCP server for the Build phase that lets Claude Code or Codex CLI drive your real Chrome with 28 tools while keeping sessions intact.
What is this MCP server?
- 28 browser tools for agent-driven control of your real Chrome session
- Preserves existing Chrome sessions and logins—no disposable headless profile required
- Works with Claude Code and Codex CLI per project description
- Chromeflow v0.9.5 with site https://chromeflow.run and GitHub NeoDrew/chromeflow
- Server version 0.9.5
- 28 browser tools documented in server description
- Repository github.com/NeoDrew/chromeflow
What problem does it solve?
Solo builders waste time re-authenticating in headless browsers when agents need to test the actual logged-in web experience they ship.
Who is it for?
Indie web builders who need agent-driven testing in real Chrome with existing cookies and SSO sessions.
Skip if: Teams that only need static scrape jobs with no personal browser session or who cannot allow local browser control for security policy reasons.
What do I get? / Deliverables
After Chromeflow is connected, your agent can run realistic UI flows in your Chrome profile so you catch breakage before users do.
- 28 MCP browser tools operating against your live Chrome profile
- Agent-executed UI paths that respect existing authentication state
Recommended MCP Servers
Journey fit
Browser driving is canonical on the Build frontend shelf when you implement and verify UI behavior in the same browser profile users rely on. Frontend subphase covers agent-assisted navigation, clicks, and verification against live pages during implementation.
How it compares
Real-profile Chrome MCP automation, not an npm security scanner or Spring OpenAPI bridge.
Common Questions / FAQ
Who is chromeflow for?
Solo developers using Claude Code or Codex CLI who ship web UIs and want agents to operate their everyday Chrome instead of a blank headless instance.
When should I use chromeflow?
Use it while building or smoke-testing frontend flows that depend on real logins, extensions, or session state you cannot easily replay in CI alone.
How do I add chromeflow to my agent?
Follow Chromeflow setup at chromeflow.run and GitHub NeoDrew/chromeflow, register the MCP server in Claude Code or Codex CLI, then enable the 28 browser tools.