ClipForge MCP

Install

Works in

• Claude Code
• Cursor
• Claude Desktop
• SourceCraft
• Koda
• Coddy

Manual install

claude mcp add clipforge -- npx -y --package https://github.com/xixihhhh/clipforge/releases/download/v0.9.7/clipforge-mcp-0.1.6.tgz clipforge-mcp

What it does

ClipForge MCP is a thin wrapper over the ClipForge application's HTTP API that Claude Desktop, Claude Code and Cursor call as a regular MCP server. The clipforge_create_video tool takes a topic in any language, writes the narration, pulls free stock video and photos from Wikimedia Commons, voices the script with Edge TTS and composes a vertical video with FFmpeg, with no paid key at all. clipforge_ingest_product takes a product link, pulls its title, price and photo from the page's markup and creates a project from that data right away. Before every compose, the narration passes through five built-in reviewer roles that break it down shot by shot, rewrite weak lines and check that a price or spec number survives the rewrite unchanged. A finished video is not treated as done on its own: the agent has to call clipforge_master to check splice continuity and loudness, then clipforge_gate, which rolls script, quality and footage-licensing checks into one verdict, and clipforge_contact_sheet to look at the frames at splice points before handing over the file link. Script generation needs one OpenAI-compatible model key; the rest of the server's tools, including stock search, the list of Edge TTS voices and export to OTIO or EDL for editing software, work key-free. The MCP server can be started key-free through an npx package from a GitHub release, but it still needs a locally running ClipForge instance with FFmpeg.

Who it is for. For marketplace sellers and short-video creators who want a finished clip from a topic or a product straight out of a chat with an agent, without a paid video-generation subscription.

Example request

Make a vertical video about how to brew pour-over coffee, with free voiceover and captions

MCP

Transport

stdio

Authentication

not required

Limitations

License is AGPL-3.0: distributing a modified version as a service means releasing that source too, so check the terms with the author before commercial use.

• The MCP server does not compose video itself: it needs a separately running ClipForge instance (`pnpm dev` or `pnpm start`) with FFmpeg installed on the same machine.
• The server package is not yet published to npm or the MCP registry; running it without cloning the repository goes through a specific GitHub release archive.
• Free video and photos come from Wikimedia Commons; better-quality stock needs separate Pexels or Pixabay keys.
• Script generation needs an OpenAI-compatible model key and spends its quota on every clipforge_create_video or clipforge_generate_script call.
• Edits to an existing video go only through a preview plan and confirmation step: applying a change without showing the diff to the agent first breaks the server's own rules.

How to disable. Remove the clipforge entry from the MCP client configuration (claude mcp remove clipforge in Claude Code, or the mcpServers block in Claude Desktop and Cursor). If the server ran through the release's npx package, no files remain besides the npx cache.

README in short

The description, in Chinese and English, opens with a comparison table against other tools on agent access: MCP, a command line, a skill and batch composition in one place. Sections on frame-composition control, a version-numbered changelog and the license follow. A closing 'Tech stack' section lists a Next.js and React front end, a route-handler API layer and test coverage run through GitHub Actions.