Chromeflow

What chromeflow MCP server does

The chromeflow MCP server connects an AI coding agent to a real, already-running Chrome session. It is intended for browser work where a fresh automation profile would be logged out or unable to complete an authentication step. The agent can interact with pages while the user retains control of credentials, two-factor authentication, payment details, and other sensitive decisions.

This places chromeflow in the 📂 Browser Automation category, but its operating model differs from tools that launch an isolated browser. Existing cookies, logged-in sessions, and installed Chrome extensions remain available. The project describes support for workflows involving services such as Stripe, AWS, Supabase, Canvas, and GitHub, without requiring the agent to re-authenticate each time.

How it works

The system has two parts: an MCP server that exposes browser actions to the coding agent, and a Chrome extension that executes those actions in the active tab. The extension can highlight page areas, perform interactions, and return page information to the agent. When a task reaches an action that should remain human-controlled, the flow can pause and ask the user to continue in Chrome.

Page interaction is based on DOM queries and browser control rather than a screenshot-only workflow. The repository documents handling for React inputs, contenteditable editors, dialogs, shadow DOM cases, and sites that require trusted-looking input events. On several social platforms, the documented workflow stops before submission: the agent prepares the content, highlights the region, and waits for the user to click Submit.

Setup and configuration

For Claude Code, add the project marketplace with /plugin marketplace add https://gitlab.com/NeoDrew/chromeflow.git, then install it with /plugin install chromeflow. Install the Chromeflow extension from the Chrome Web Store and restart Claude Code. The plugin registers the MCP server and includes its usage skill.

For Codex CLI, add the marketplace with codex plugin marketplace add https://gitlab.com/NeoDrew/chromeflow.git, run /plugins install chromeflow inside Codex, install the same Chrome extension, and restart Codex. The extension is shared by both supported agent environments. The README describes a plugin-based installation and does not specify environment variables or per-project configuration.

Tools and capabilities

Documented browser operations include opening pages, clicking elements, filling forms, setting file inputs, reading page text, and writing captured values to .env. The project description refers to a larger tool set for browser control, while the setup documentation specifically names these operations.

The server can support workflows such as retrieving API keys from a logged-in dashboard and saving them to a project environment file. It can also assist with composing text in web applications, including editors based on Lexical, Quill, TipTap, or ProseMirror, where the listed validation covers particular interactions.

Limitations and notes

The user must have Chrome and the extension installed, and the relevant session must be available in that browser. Sensitive steps are intentionally not fully automated. Password entry, 2FA, payment actions, and final submission on some anti-bot-protected sites may require a manual action.

Validated behavior is platform- and interaction-specific, not a guarantee that every page or control will work. The repository lists tested cases for Reddit, X/Twitter, LinkedIn, Facebook, Instagram, Radix dialogs, closed shadow DOM, and TipTap/ProseMirror. These validations describe particular actions such as typing or opening a composer, rather than unrestricted automation of each platform.