Chromeflow MCP
- 2 repo stars
- Updated May 13, 2026
- NeoDrew/chromeflow
Chromeflow is a MCP server that lets Claude Code or Codex CLI drive your real Chrome with 28 tools while keeping sessions intact.
About
Chromeflow is an MCP server that attaches your coding agent to the Chrome browser you already use, with 28 tools for navigation, interaction, and inspection while cookies and sessions stay intact. developers shipping web apps, extensions, or SaaS dashboards use it when headless automation cannot reproduce logged-in states or third-party OAuth flows. During build—and often while validating a prototype—you can have Claude Code or Codex CLI exercise checkout paths, admin panels, or marketing pages without manually clicking through every regression. Chromeflow is browser automation infrastructure, not a test framework reporter; pair it with your own review habits. Version 0.9.5 is published with documentation at chromeflow.run.
- 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
Chromeflow MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | May 13, 2026 |
| Repository | NeoDrew/chromeflow ↗ |
What it does
Let Claude Code or Codex CLI control your logged-in Chrome for real UI checks, flows, and demos without rebuilding auth in headless browsers.
Who is it for?
Best when you need agent-driven testing in real Chrome with existing cookies and SSO sessions.
Skip if: Skip if you only need static scrape jobs with no personal browser session or and cannot allow local browser control for security policy reasons.
What you get
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
By the numbers
- Server version 0.9.5
- 28 browser tools documented in server description
- Repository github.com/NeoDrew/chromeflow
Recommended MCP Servers
1stDibs MCPMCP server for browsing and searching items on 1stDibs marketplace.
2Captcha MCPFull 2Captcha API (43 tools) for Claude Code: 31 captcha solvers + management + webhook.1
4fetch MCPFetch a URL and get clean Markdown with metadata.
Acrawl MCPAutonomous web crawler.11
Agentfetch MCPToken-budgeted web fetch for AI agents — auto-routes Jina, FireCrawl, Trafilatura, PDF.3AgenticTotem Web Extractor MCPAI web extraction: send URLs + a JSON Schema, get clean structured data.How it compares
Real-profile Chrome MCP automation, not an npm security scanner or Spring OpenAPI bridge.
FAQ
Who is chromeflow for?
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 MCP setup at chromeflow.run and GitHub NeoDrew/chromeflow, register the MCP server in Claude Code or Codex CLI, then enable the 28 browser tools.