Skip to main content
Glama
Sign In
iLoveVideoEditor MCP Server

iLoveVideoEditor MCP Server

Official
by ilovevideoeditor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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"
      }
    }
  }
}

Related MCP server: json2video MCP Server

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

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

Available Tools

10 tools
ilovevideoeditor_get_download_urlA

Get a fresh signed download URL for a completed render job.

Inputs: jobId (required).

ilovevideoeditor_get_layer_capabilitiesA

Return the built-in effects and transitions that are compatible with a given layer type (text, image, video, shape, audio, etc.). Use this before choosing effects or transitions for a layer.

Inputs: layerType (required), includeMetadata.

ilovevideoeditor_get_render_statusB

Check the status of a render job by its job ID.

Inputs: jobId (required).

ilovevideoeditor_get_templateA

Get detailed information about a specific template, including its variable schema.

Inputs: templateId (required).

ilovevideoeditor_list_templatesA

List all available iLoveVideoEditor templates for generating personalized videos.

Inputs: no named parameters.

ilovevideoeditor_local_analyzeA

Analyze the generated VideoJSON layout in the local preview and return structured metrics and issues (overflow, overlap, font fallback, etc.).

Inputs: time.

ilovevideoeditor_local_captureB

Capture a screenshot from the running local preview at a given time.

Inputs: time, format.

ilovevideoeditor_local_previewA

Start or stop the local preview dev server. Use this before capturing frames.

Inputs: action (required), file.

ilovevideoeditor_render_jsonA

Submit a raw VideoJSON payload to the iLoveVideoEditor render queue and receive a job ID.

Inputs: videoJSON (required).

ilovevideoeditor_render_templateA

Generate a video from a named template with variables, queue it for rendering, and return a job ID.

Inputs: variables (required), templateId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Resources

    Related MCP Connectors

    Related MCP Servers