The MCP server renders videos from JSON using iLoveVideoEditor motion-design templates and effects. It accepts MCP clients to list templates, fill variables, submit JSON-to-MP4 render jobs, poll status, and obtain download URLs.

🛠️ Key Features

Lists motion-design templates from iLoveVideoEditor
Accepts JSON input to render MP4 videos
Submits and manages batch render jobs
Polls job status and exposes download URLs
API-key protected integration via dashboard

🚀 Use Cases

AI agents rendering templated videos with variable data
Batch video production from structured JSON payloads
Integrating video generation into MCP-enabled workflows

⚡ Developer Benefits

Standard MCP protocol compatibility (Model Context Protocol)
Clear, template-driven rendering workflow
Programmatic access to status and download endpoints

⚠️ Limitations

Requires an API key from the iLoveVideoEditor dashboard
Depends on iLoveVideoEditor templates and available resources
Documentation scope based on available readme excerpt; behavior may evolve with API updates

iLoveVideoEditor MCP Server

Model Context Protocol (MCP) server that lets AI agents (Claude, ChatGPT, Cursor, and any MCP client) render videos with iLoveVideoEditor: list motion-design templates, fill in variables, submit JSON-to-MP4 render jobs, poll status, and get download URLs.

Quick start

Get an API key from the dashboard: ilovevideoeditor.com/dashboard/account/api

Add the server to your MCP client config:

json

{
  "mcpServers": {
    "ilovevideoeditor": {
      "command": "npx",
      "args": ["-y", "@ilovevideoeditor/mcp-server"],
      "env": {
        "VF_API_KEY": "vf_live_xxx"
      }
    }
  }
}

Tools

Tool	Description
`ilovevideoeditor_list_templates`	List available templates
`ilovevideoeditor_get_template`	Get template details and variable schema
`ilovevideoeditor_render_json`	Submit raw `VideoJSON` for rendering
`ilovevideoeditor_render_template`	Render from a named template + variables
`ilovevideoeditor_get_render_status`	Poll render job status
`ilovevideoeditor_get_download_url`	Get signed download URL

Configuration

Variable	Default	Description
`VF_API_KEY`	—	Required. Your iLoveVideoEditor API key (`x-api-key`)
`VF_API_BASE_URL`	`https://api.ilovevideoeditor.com`	API base URL override

Development

bash

npm install
npm run build    # tsc -> dist/
npm start        # stdio transport
npm run dev      # tsx watch

The server speaks MCP over stdio (diagnostics go to stderr). An optional --http flag enables HTTP/SSE transport for debugging.

Source of truth lives in the iLoveVideoEditor monorepo (integrations/mcp-server); this repository is the public mirror used for releases.

License

Apache-2.0

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

iLoveVideoEditor MCP Server

Quick start

Tools

Configuration

Development

License

Install

Configuration