| FMRS | 66 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 |
|---|
| Maintenance | 15 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 |
|---|
| Best for | - AI agent builders who want local video editing, captioning, repurposing, and quality gating
- Developers and creators already using MCP clients such as Claude Code or Cursor
- Local media operators who want typed, guardrailed FFmpeg operations with traceable artifacts instead of guessed flags
| - 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 who want a hosted cloud editor or credit-metered SaaS
- Users who want an untyped shell wrapper for arbitrary FFmpeg commands
- Anyone unwilling to install FFmpeg (and optionally Node.js, Whisper, and other extras) locally
- People expecting to edit raw Insta360 .insv or GoPro .360 files directly — you must export a stitched equirect MP4 from the camera app first
| - 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 | - Read and write local media files and output directories (editing, exporting, receipts)
- Execute local FFmpeg/ffprobe subprocesses
- Read local project/data directories (for example the ~/.mcp-video compatible data dir)
- Optional: network access for Hyperframes features, website capture, or installing Python extra dependencies
- Optional: C2PA signing requires c2patool plus a local manifest/signer
| - 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 | - Agents may produce poor or broken video: the README explicitly requires video_quality_check, release checkpoints, and human visual/audio inspection before publishing
- Risk of overwriting source media: rescue and derivative flows claim the source stays immutable, but you should still back up important footage
- Optional extras are large (transcribe ~1 GB, stems ~2 GB, upscale ~2 GB), consuming significant disk and install time
- Depends on a local external toolchain (FFmpeg, plus Node.js 22+ for Hyperframes), so environment drift causes failures
- Optional capabilities such as website capture, local speech, or AI background removal may involve network access and extra licensing/compliance review
- Some README surfaces (desktop MCPB packaging, deeper Sonic World Audio integration, the trusted execution kernel, generative spend-cap plans) are gated, partial, or unreleased and should not be treated as stable shipped features
| - 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 clients | Claude Code, Claude Desktop, Cursor | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 19 | 26 |
|---|