ReelMint ships a built-in MCP server. Connect Claude Desktop, Claude Code, or Cursor with a workspace-scoped token, and “make a 60-second reel from my post” becomes a working command — you review, it does the clicking.
Built-in MCP server — works with Claude Desktop, Claude Code, Cursor, and any MCP-capable agent, scoped to your workspace.
Your token lives on the MCP & Agents page inside the studio — scoped to one workspace, rotatable in one click.
| Tool | What it does |
|---|---|
| draft_script | Write a scene-by-scene script from a topic, URL, or your knowledge base |
| author_scenes | Compose each line into motion-graphic scenes from the component catalog |
| preview_scene | Render film-strip frames of any scene in seconds — look before you render |
| synthesize_scene_voice | Narrate a scene and lock its timing to the audio automatically |
| compose_video | Render the full 9:16 Short on the fair queue, within your daily budget |
| publish_reel | Upload to your YouTube channel — as a draft you approve, or scheduled |
Anything that speaks MCP: Claude Desktop, Claude Code, Cursor, Cline, Continue, or your own agent via the open protocol. One config entry connects them.
The full pipeline: draft scripts, author scenes from the component catalog, preview frames, synthesize narration, compose the video, and publish to YouTube — the same guarded endpoints the UI uses.
Every workspace has a daily render budget and a fair render queue, so a runaway loop cannot melt the studio or surprise you. Tokens are workspace-scoped and rotate in one click.
No. The MCP server is part of every workspace, including the free pilot. Generation runs on your own API keys, like everything else.
Free pilot, workspace-scoped token, daily budgets on. No credit card.
Claim a pilot spot