com.ilovevideoeditor/mcp-server

Official registry Media and design

Render videos from VideoJSON + 249+ templates via the iLoveVideoEditor API

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @ilovevideoeditor/mcp-server
Claude Code
claude mcp add com-ilovevideoeditor-mcp-server -e 'VF_API_KEY=<your vf_api_key>' -e 'VF_API_BASE_URL=https://api.ilovevideoeditor.com' -- npx -y @ilovevideoeditor/mcp-server@1.0.1
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "com-ilovevideoeditor-mcp-server": {
            "command": "npx",
            "args": [
                "-y",
                "@ilovevideoeditor/mcp-server@1.0.1"
            ],
            "env": {
                "VF_API_KEY": "<your vf_api_key>",
                "VF_API_BASE_URL": "https://api.ilovevideoeditor.com"
            }
        }
    }
}

Environment variables

  • VF_API_KEY required secret iLoveVideoEditor API key (x-api-key) from the dashboard
  • VF_API_BASE_URL iLoveVideoEditor API base URL override

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. iLoveVideoEditor MCP Server
  2. Quick start
  3. Tools
  4. Configuration
  5. Development
  6. License

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:

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

Tools

ToolDescription
ilovevideoeditor_list_templatesList available templates
ilovevideoeditor_get_templateGet template details and variable schema
ilovevideoeditor_render_jsonSubmit raw VideoJSON for rendering
ilovevideoeditor_render_templateRender from a named template + variables
ilovevideoeditor_get_render_statusPoll render job status
ilovevideoeditor_get_download_urlGet signed download URL

Configuration

VariableDefaultDescription
VF_API_KEY—Required. Your iLoveVideoEditor API key (x-api-key)
VF_API_BASE_URLhttps://api.ilovevideoeditor.comAPI base URL override

Development

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

Frequently asked questions

What is com.ilovevideoeditor/mcp-server?

Render videos from VideoJSON + 249+ templates via the iLoveVideoEditor API

How do I install com.ilovevideoeditor/mcp-server?

It runs on your machine. In Claude Code: claude mcp add com-ilovevideoeditor-mcp-server -e 'VF_API_KEY=<your vf_api_key>' -e 'VF_API_BASE_URL=https://api.ilovevideoeditor.com' -- npx -y @ilovevideoeditor/mcp-server@1.0.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does com.ilovevideoeditor/mcp-server need an API key?

Yes. It expects VF_API_KEY, which you set in its configuration.

Is com.ilovevideoeditor/mcp-server open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains com.ilovevideoeditor/mcp-server?

It is published by ilovevideoeditor. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.