json2video-mcp-server

Json2video MCP Server

JSON-defined video projects connect LLMs and automation agents to the json2video API. The integration supports scene composition, asynchronous render checks, and template creation and retrieval through MCP-compatible clients.

Server facts

json2video-mcp-server

Project

License
Not specified

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
26
Last commit
Data as of

Overview

Video composition through json2video starts with a structured project passed to generate_video. LLMs, automation agents, and other MCP clients can describe scenes containing images, text, audio, video clips, HTML, components, voice, audiograms, and subtitles. Elements can also sit at the project level rather than inside individual scenes. Project settings cover quality, resolution, variables, and custom dimensions; choosing a custom resolution requires both width and height. Rendering runs asynchronously, so the initial response supplies a project identifier rather than a finished video. The get_video_status tool uses that identifier to request progress or retrieve the result, with further checks needed while rendering remains unfinished.

Template operations provide a separate workflow alongside video generation. create_template accepts a name and an optional description, get_template retrieves a template by name, and list_templates returns the templates available to the user. Authentication uses a json2video API key supplied through an environment variable or with an individual request. The Node-based integration communicates over stdio, and the documentation includes setup guidance for Cursor and other MCP client configurations.

json2video-mcp-server setup notes

  • json2video-mcp-server records stdio only; confirm a network transport upstream before planning remote access.
  • json2video-mcp-server has no recorded license; confirm reuse terms in its repository.

Related MCP servers