Render videos from JSON with motion-design templates, effects and batch rendering
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.
Get an API key from the dashboard: ilovevideoeditor.com/dashboard/account/api
Add the server to your MCP client config:
{
"mcpServers": {
"ilovevideoeditor": {
"command": "npx",
"args": ["-y", "@ilovevideoeditor/mcp-server"],
"env": {
"VF_API_KEY": "vf_live_xxx"
}
}
}
}
| 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 |
| 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 |
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.
Apache-2.0
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @ilovevideoeditor/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-ilovevideoeditor-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ilovevideoeditor/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@ilovevideoeditor/mcp-servernpmio.github.ilovevideoeditor/mcp-server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.