iLoveVideoEditor MCP Server
OfficialRelated Servers
Alternatives to iLoveVideoEditor MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables programmatic video generation via the json2video API, supporting scene and element creation, status polling, and template management.52326MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to create, monitor, cancel, and download cinematic AI video renders through the Future Video Studio Agent API.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to edit videos through natural language, providing tools for timeline editing, audio management, rendering, and more.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to validate and render branded videos from structured Video Specifications via the Model Context Protocol. Provides tools for health checks, video validation, and deterministic Remotion rendering.-
- AlicenseAqualityCmaintenanceEnables MCP-compatible agents to access KaiRouter's video generation API, providing tools to list available video models, generate videos (text-to-video or image-to-video) asynchronously, check job status, and list recent jobs.4MIT
- AlicenseBqualityBmaintenanceEnables AI assistants and coding agents to automate Pictory.ai video creation, including 1080p rendering, transcription into viral short clips, AI avatars, stock asset search, project/template management, and publishing to Vimeo and S3.5MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: template listing/detail, layer capabilities, two render submission methods, status/dowload retrieval, and local preview/capture/analyze. No two tools appear to overlap or cause selection confusion.
All tools share the 'ilovevideoeditor_' prefix followed by lowercase snake_case action_noun or action_target_pattern. The 'local_' prefix groups preview/capture/analyze consistently, and the naming convention is uniform and predictable.
With 10 tools, the set is well-scoped for a video editing/render server, covering template exploration, rendering, status, download, and local preview workflows. Each tool earns its place without bloat.
The tool surface covers the main lifecycle: discover templates, render, check status, obtain download URL, and local preview/analyze. A minor gap is the lack of job cancellation or listing, but the core workflow is complete and agent usable.