| FMRS | 66 / 100 · C | 75 / 100 · B |
|---|
| Reliability | 10 / 20 | 10 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 |
|---|
| Maintenance | 15 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 14 / 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
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| 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 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 | - 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 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 | - 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
| - 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 clients | Claude Code, Claude Desktop, Cursor | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 19 | 11 |
|---|