Install the Video MCP Server and Verify It Without Rendering

Install the Video MCP Server and Verify It Without Rendering

An agent integration should establish a safe read-only path before it can spend credits or create an output. The sequence below keeps the API key in the client environment and makes the first proof observable.

Prerequisites

Use an MCP-compatible client, Node.js 22 or newer, and a server-side VF_API_KEY. Put the key in the local client environment or secret store; never paste it into a prompt, commit it to a config file, or send it to a transcript service.

Install and configure

Run the published MCP server from the client configuration:

npx -y @ilovevideoeditor/mcp-server

The server exposes typed tools for templates, planning, rendering, local preview, and text measurement. Keep the command and key configuration local to the client that launches it.

Safe verification

Start with list_templates, then call get_template for one known template and measure_text with a short, non-sensitive string. These calls verify process startup, tool discovery, schema validation, and a deterministic utility without rendering. If the client cannot list tools, fix the process or environment before trying render_template or render_json.

First render boundary

Only after read-only verification should an agent plan a composition, check layer capabilities, and ask for an explicit render. A render request should include approved assets, a reviewable brief, and a human checkpoint before distribution. get_render_status and get_download_url are delivery steps, not proof that the output is publishable.

Failure modes and redaction

If the client cannot launch npx, check its runtime path and network policy. If the key is missing, fix the environment rather than including it in the conversation. Redact API keys, private URLs, customer names, and full transcripts from logs and support captures. Keep the tool name, error class, and sanitized request shape so the failure can still be reproduced.

Tested version and next step

This guide was checked against MCP server v1.0.2 and the tools contract on 2026-08-05. Continue with the MCP tool catalog, then use the brief-to-render pattern when the read-only path is stable.