io.github.NeoDrew/chromeflow MCP Server
io.github.NeoDrew/chromeflow
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
What is the io.github.NeoDrew/chromeflow MCP server?
Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.
How to install io.github.NeoDrew/chromeflow
Copy-paste configuration for popular MCP clients.
No machine-readable install method is published for this server in the registry. Check the repository or website for setup instructions.
Related MCP servers

DispatchSEO
AI-powered SEO manager: keyword research, content PRs, and rank tracking for coding agents.

Askell
MCP server for the Askell payment and subscription API (Bun + stdio)

Agent Droid Bridge
AI agents control Android devices and emulators via ADB for mobile automation, testing, and analysis.
Wrap any korg:introspect@v1-aware binary as a Claude Code tool, honoring declared side-effects.
AI/ML engineering MCP server for Neo — submit tasks, track execution, and retrieve outputs.
View repository →
Verify trading-strategy backtests: look-ahead probes, trading costs, Deflated Sharpe, walk-forward.

