iLoveVideoEditor MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VF_API_KEY | Yes | Your iLoveVideoEditor API key (x-api-key). Required. | |
| VF_API_BASE_URL | No | API base URL override | https://api.ilovevideoeditor.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ilovevideoeditor_list_templatesA | List all available iLoveVideoEditor templates for generating personalized videos. |
| ilovevideoeditor_get_templateA | Get detailed information about a specific template, including its variable schema. |
| 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. |
| ilovevideoeditor_render_jsonA | Submit a raw VideoJSON payload to the iLoveVideoEditor render queue and receive a job ID. |
| ilovevideoeditor_render_templateA | Generate a video from a named template with variables, queue it for rendering, and return a job ID. |
| ilovevideoeditor_get_render_statusB | Check the status of a render job by its job ID. |
| ilovevideoeditor_get_download_urlA | Get a fresh signed download URL for a completed render job. |
| ilovevideoeditor_local_previewA | Start or stop the local preview dev server. Use this before capturing frames. |
| ilovevideoeditor_local_captureB | Capture a screenshot from the running local preview at a given time. |
| ilovevideoeditor_local_analyzeA | Analyze the generated VideoJSON layout in the local preview and return structured metrics and issues (overflow, overlap, font fallback, etc.). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.