# Chromeflow

> Chromeflow is an MCP server for browser automation. MCP server letting Claude Code and Codex CLI drive your existing Chrome session. It is available on CLI, macOS, Windows and Linux.

- **Kind:** MCP server
- **Platforms:** CLI, macOS, Windows, Linux
- **Website:** https://chromeflow.run
- **Repository:** https://gitlab.com/neodrew/chromeflow
- **MCP Registry name:** run.chromeflow/chromeflow
- **Categories:** [browser automation](https://ai-powered.com/categories/browser-automation)
- **Listing updated:** 2026-11-18

## About

Chromeflow connects coding agents such as Claude Code and Codex CLI to the Chrome browser you already use, so they operate with your logged-in state rather than a fresh sandboxed browser. According to its website, the agent can click through pages, fill in forms, collect API keys from dashboards and write them into a .env file.

The server is distributed as a single MCP package exposing 28 browser tools to the client. Because it reuses the real session and cookies, it suits tasks that require authenticated pages, where a clean headless browser would be logged out.

It is aimed at developers who already work in terminal-based coding agents and want them to handle setup chores in web consoles. Users should weigh the access it gives an agent to a signed-in browser.

## Features

- **Real session reuse:** Operates inside your existing Chrome profile, keeping current logins and cookies intact.
- **28 browser tools:** Exposes a set of 28 browser actions to the MCP client, as described on the product page.
- **Form filling and clicks:** Lets the agent click elements and fill in form fields on web pages.
- **API key capture to .env:** Retrieves keys from dashboards and writes them into a local .env file.
- **Claude Code and Codex CLI support:** Works with both Claude Code and Codex CLI as MCP clients.

## Good for

- Pulling API keys from provider dashboards into a project .env file
- Filling repetitive web forms while a coding agent works in the terminal
- Driving an authenticated web app that a headless browser cannot access
- Automating multi-step admin tasks in a browser already signed in

## FAQ

### Which AI clients does Chromeflow work with?

The product page and registry entry name Claude Code and Codex CLI.

### Does it use a fresh browser or my existing one?

It uses your real Chrome with its sessions and cookies rather than a new sandbox browser.

### How many tools does the server provide?

The listing states 28 browser tools.

### What are the best alternatives to Chromeflow?

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

## Where this comes from

- Description: written from the project's website and its MCP Registry entry.

## Alternatives

- [Chrome DevTools MCP](https://ai-powered.com/mcp/chrome-devtools-mcp-4): Chrome DevTools MCP is an open-source MCP server for browser automation.
- [Agent360 Browser MCP](https://ai-powered.com/mcp/agent360-browser-mcp): Agent360 Browser MCP is an open-source MCP server for browser automation.
- [Tether](https://ai-powered.com/mcp/tether-2): Tether is an open-source MCP server for browser automation.
- [pilotfish (local)](https://ai-powered.com/mcp/pilotfish-local): pilotfish (local) is a freemium MCP server for browser automation.
- [NextCore Browser](https://ai-powered.com/mcp/nextcore-browser): NextCore Browser is a freemium MCP server for browser automation.
- [CloudBrowser](https://ai-powered.com/mcp/cloudbrowser): CloudBrowser is an MCP server for browser automation.
- [Browser.lol](https://ai-powered.com/mcp/browser-lol): Browser.lol is a paid MCP server for browser automation.
- [MCP Browser Extension](https://ai-powered.com/mcp/mcp-browser-extension): MCP Browser Extension is an open-source MCP server for browser automation.

---
Source: https://ai-powered.com/mcp/chromeflow-2
