Skip to content
MCP server

Chromeflow

MCP server letting Claude Code or Codex CLI drive your logged-in Chrome browser

Pricing
Open source
Platforms
CLI, Chrome extension, macOS
Version
0.9.5
Listing updated
today

Similar MCP servers

About Chromeflow

Chromeflow is an open-source MCP server for browser automation. It is available on CLI, Chrome extension, macOS, Linux and Windows.

Chromeflow connects a coding agent to the Chrome browser you already use, so it keeps your existing logins, cookies and sessions instead of starting a blank automated browser. The README describes it as two parts: an MCP server that exposes browser tools to the agent, and a Chrome extension that performs the actions on the active tab.

The agent handles routine steps such as clicking, filling forms, uploading files and reading API keys from a page, then writes captured values to a local .env file. For passwords, two-factor codes or payment details it pauses and hands control back to the user, using highlights and a wait-for-click tool.

The project is aimed at developers who set up third-party services such as Stripe, Supabase or SendGrid from inside a coding session. It supports running several agent sessions in parallel, each bound to its own Chrome window.

Tools this server provides (12)

Taken from the project documentation; the running server may differ.

open_page
Navigate to a URL or open a new tab.
click_element
Click buttons and links, with optional nth for duplicates.
fill_input
Fill a single form field.
fill_form
Fill multiple fields in one call.
set_file_input
Upload a file to a file input, including hidden ones.
get_page_text
Read page content as text, optionally scoped by selector.
write_to_env
Write captured values to a .env file.
take_screenshot
Capture a screenshot of the page.
capture_terminal
Screenshot the terminal window and save as PNG.
highlight_region
Highlight elements for the user.
wait_for_click
Wait for the user to click an element.
execute_script
Run arbitrary JavaScript on the page.

What it does

Uses your real Chrome
Actions run in your existing logged-in browser profile rather than a fresh instance.
Pauses for sensitive input
The agent hands control back to you for logins, 2FA and payment steps.
Captures keys to .env
Values read from a page, such as API keys, can be written to a local .env file.
File upload support
set_file_input can upload files, including through hidden file inputs.
Parallel agent sessions
Up to 11 sessions can each drive a separate Chrome window on their own port.
Terminal screenshots
capture_terminal saves a PNG of the terminal window for sharing into web forms.

Good for

  • Copy API keys from a service dashboard into a project's .env file
  • Set up Stripe products and pricing from inside a Claude Code session
  • Fill out a web form using data the coding agent has gathered
  • Run research in one Chrome window while another agent session works in a different one

Pricing

Open source

Prices change. Check chromeflow.run before you buy.

Chromeflow FAQ

Which AI clients does it work with?

The README says it works with Claude Code and Codex CLI, installed as a plugin for each.

What browsers are supported?

The README lists Chrome, or any Chromium browser, and requires Node.js 22 or newer.

Does it handle logins and two-factor authentication?

It uses your existing logged-in session and pauses for passwords, 2FA and payment details so you complete them yourself.

Why not use Playwright or Puppeteer?

The README contrasts this with those tools, which launch fresh logged-out browsers. Chromeflow instead uses your own Chrome profile.

Is Chromeflow free?

Yes. Chromeflow is open source, so you can use and self-host it for free.

What are the best alternatives to Chromeflow?

The closest alternatives to Chromeflow are Agent360 Browser MCP, Tether, Agent Chrome, Chrome DevTools MCP and pilotfish (local).

Where this comes from

  • Description: written from the project's README, the project's website and its MCP Registry entry.

How AIPoweredBot checks servers