Moviola Protocol MCP
Related Servers
Alternatives to Moviola Protocol MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to perform deterministic FFmpeg video edits—silence removal, vertical reframing, 3D LUT grading, and metadata/audio extraction—and generate native CapCut Desktop drafts, with a local web studio for previewing and batch processing.51MIT
- AlicenseAqualityBmaintenanceDeterministic Model Context Protocol (MCP) server for FFmpeg. Gives AI agents 17 structured tools with hardware acceleration for video conversion, compression, waveforms, subtitles, and inspection.19349 npm4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to edit video locally through FFmpeg: probing media, validating and previewing JSON edit projects, rendering short-form clips with captions, reframing, transitions and ducked music. Also analyses existing videos and applies or saves reusable format templates, without cloud services or API keys.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to convert local videos into styled ASCII art by inspecting source metadata, previewing and visually judging rendered frames, exploring preset parameters, and exporting finished clips. Supports MP4 with audio or GIF output with trimming, speed changes, reframing, beat-synced styles, and shareable editor links, all processed locally.MIT
- AlicenseBqualityCmaintenanceProvides Claude Code with local ffmpeg-based tools to probe, trim, concat, transform, overlay, mix audio, render JSON timelines, and run automated QA on video files—no API key required.9Apache 2.0
- AlicenseAqualityCmaintenanceEnables local video inspection and offline transcription with timestamped JSON and Markdown output, enforced filesystem boundaries, and reproducible content-addressed caching.2MIT
TDQS
Scored across 11 tools
Most tools have a clearly distinct purpose: media processing (probe_media, convert_media, slideshow_from_images), index queries (index_history, index_stats, index_chains), and training export (training_backends, export_training_data). The three index_* tools overlap somewhat but their descriptions distinguish them (recent conversions vs. per-preset aggregates vs. chained files). Only minor confusion between convert_media and export_training_data from the description wording, since export also converts media.
Mostly snake_case with a verb_noun pattern (probe_media, convert_media, list_presets, install_opencode_plugin, export_training_data), but there are noun-first and bare-noun deviations: slideshow_from_images, doctor, and training_backends. The three index_ tools form a visible family but use index_ as a noun-ish prefix rather than a verb. Readable overall, but not a clean consistent convention.
Eleven tools is well-scoped for a media-processing-plus-training-export server. Each tool has a clear responsibility, with no filler or trivially redundant entries.
The surface covers the core lifecycle: probing, conversion, slideshow assembly, preset discovery, environment diagnosis, history/stats/chains, plugin installation, and training export. Minor gaps exist: no batch conversion of many files at once (probe is single-file), and no way to delete/clear database records or fetch a single conversion's details.