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.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS36 / 100 · D77 / 100 · B
Reliability6 / 2012 / 20
Security and permissions8 / 2016 / 20
Maintenance7 / 2016 / 20
Documentation10 / 2018 / 20
Setup experience5 / 2015 / 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
  • Hevy PRO users who want AI assistants to directly access their workout data
  • People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
  • Anyone needing summaries and insights from their training data
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 without a Hevy PRO subscription (API key required)
  • Users who want to use the server without an API key
  • Those needing delete workflows (Hevy API does not expose delete endpoints)
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 HEVY_API_KEY environment variable for Hevy API authentication
  • Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
  • Read operations can fetch workouts, routines, folders, templates, history, and user info
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
  • API key can be misused if leaked; do not expose in URLs, logs, or screenshots
  • Create operations may produce duplicates on retry; update operations replace existing records
  • The server sends data to the Hevy API and may send telemetry to external services unless disabled
Supported clientsClaude CodeClaude Desktop, Cursor, Codex, Antigravity
Tools026