Chromeflow

run.chromeflowPublished by chromeflow.runv0.9.8Updated Oct 25, 2026

Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.

VerifiedSTDIODesktop onlyBrowser Automation

Overview

AI-generated overview

Chromeflow lets Claude Code or Codex CLI drive your real Chrome browser with existing sessions intact, exposing 28 browser tools.

What you can do
Drive a real Chrome browser from the assistant, keeping existing sessions intact rather than starting a fresh profile. Access a set of 28 browser tools for interacting with pages. Runs locally as a desktop-only process connected over stdio.
When to use it
Useful when you want an AI coding assistant to operate the Chrome browser you already use, with your logged-in sessions available, for example to check or interact with web pages during development.
Requirements
Runs as a local process on the user's machine over stdio. Desktop only; no web executable. No packages, authentication, environment variables or headers are declared.
Before you install
It drives your real Chrome with your existing sessions intact, so the assistant can act within accounts you are logged into. Review what actions it takes before granting it control.

Installation

In SourceWeft

  1. Open Chromeflow in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.9.8LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.