Chromeflow runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 17 Sep 2026.
Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.
What the code does
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
execSync(
matrix.innerHTML = PLATFORMS.map(p => {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Chromeflow
same job, measured the same wayLets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.
Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.
Browser control + session recording MCP for AI coding agents (Claude Code, Cursor) — real Chrome.
86 tools: drive YOUR real Chrome via CDP + browse/install/publish Threads in chat. webloom.run.
MCP server + Chrome extension for AI browser control with real sessions.
Bridge a live Chrome browser to your agent: 150 tools for capture, extraction, and observation.
Browser sessions, checkpoints, rewind, fork, lineage, and lifecycle tools for brawsr.
MCP server that drives the real Chrome you already use, through an extension and CDP.
Chromeflow — questions
Answers built from our own checks of this server.