M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

Dimensiongflow-cli MCP ServerDrive Google Flow's Veo video and Imagen image generation from the CLI or an AI agent.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS36 / 100 · D75 / 100 · B
Reliability6 / 2010 / 20
Security and permissions8 / 2016 / 20
Maintenance7 / 2018 / 20
Documentation10 / 2017 / 20
Setup experience5 / 2014 / 20
Best for
  • Heavy users who need scripted, batched, or pipeline-ready Flow generation
  • Automation and AI-video projects that want to expose Flow generation to agents
  • Developers with Google Flow access and Veo credits outside restricted regions
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users expecting official Google support or an official API
  • Users unwilling to accept account-automation risk or spend their own Flow credits
  • Users needing headless pure-HTTP or serverless browserless deployment
  • Users wanting to redistribute or resell the tool beyond Google's services
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Requires the user's own logged-in Google Flow session and account credentials
  • Persists a local Playwright Chromium profile (default per-user directory, configurable via GFLOW_CLI_HOME)
  • Writes generated outputs to a local output directory (or via GFLOW_CLI_STORAGE_URI to S3, MinIO, or Google Cloud Storage)
  • Reaches Google's private Flow interfaces (aisandbox-pa.googleapis.com or the migrated batchexecute endpoint)
  • Video generation spends Flow credits on that account
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • The tool is alpha and reverse-engineered with no Google affiliation, and can break when Google's endpoints or UI change without notice
  • Automation is subject to Google's ToS and carries account-flagging risk; the project deliberately uses no proxies, no fingerprint spoofing, and does not pretend it isn't automation
  • Video generation spends real credits; when the UI drifts the CLI fails fast and loudly (e.g. selector drift = exit 23) rather than resubmitting
  • The MIT license covers only its code and grants no rights to Flow, Veo output, or any Google service
  • Installing from a local checkout without pinning Playwright can pull an untested browser driver that silently wedges generation
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011