Mocut for Claude Code
Let Claude edit your video in the Mocut editor while you watch: cuts, captions, titles and motion graphics. Every change shows up live and can be undone.
Set it up with one prompt
Paste this into Claude Code (the Claude desktop app's Code tab, or the claude terminal app):
Read https://mocut.app/claude and set up Mocut for me.
Works on every Mocut plan, including Free.
Instructions for Claude
You are setting up the Mocut MCP server (https://mcp.mocut.app/mcp) for this user. Do these steps in order and tell the user briefly what you did after each one.
-
Check whether Mocut is already added. If Mocut's tools (such as
get_editor_state) are already available in this session, Mocut is connected: skip to step 4. Otherwise run:claude mcp get mocut
If it shows
https://mcp.mocut.app/mcpwithScope: User configandConnected, Mocut is ready: skip to step 4. If it shows the address withNeeds authenticationandScope: User config, skip to step 3. If it is missing or set up only for one folder (Local configorProject config), continue with step 2. -
Add Mocut for every folder. Run:
claude mcp add --transport http --scope user mocut https://mcp.mocut.app/mcp
If the
claudecommand is not found (common in the Claude desktop app on a Mac), use the copy bundled with the desktop app. Find the newest one with:ls -d "$HOME/Library/Application Support/Claude/claude-code"/*/*/claude.app/Contents/MacOS/claude | tail -1
and run the same commands with that path in place of
claude. If you cannot run Claude Code commands at all, give the user the "Without a terminal" steps below instead and stop. -
Start the sign-in. Tell the user first: "Your browser will open Mocut's page. Sign in to Mocut, check that it says Claude Code, and click Allow." Then run:
script -q /dev/null claude mcp login mocut
The sign-in needs a terminal, which
scriptprovides when you run commands for the user (macOS). On Linux usescript -q -c "claude mcp login mocut" /dev/null. In a terminal the user types into, plainclaude mcp login mocutworks. It opens the browser and waits until the user clicks Allow, so allow it up to 5 minutes; it printsAuthenticated with "mocut"when done. If it still cannot sign in, ask the user to type/mcpin Claude Code, choose mocut and then Authenticate. -
Open your own editor window. If you run inside the Claude desktop app (its Code tab has a built-in Browser pane beside the chat), open
https://editor.mocut.app/?agent-window=1in that pane (itspreview_starttool with the url), not in Claude in Chrome, and keep it in view: it is your own Mocut window, and calls go to it before any other tab. Ask the user to sign in there once and click Allow in the bar at the top. Without a built-in browser, ask the user to open editor.mocut.app, open the project they want edited, and turn on Account menu → Connected agents → Allow connected agents. -
Finish. Mocut's tools load when a Claude Code session starts. Tell the user to start a new session and ask for an edit, for example "Add captions to my video" or "Make an animated title for the intro".
How to work with Mocut (for Claude, in later sessions)
- Start with
get_editor_state, thenget_timeline. Name every clip or track by id: no tool uses the user's selection unless you pass its ids. - Before writing motion graphics, read
get_mocut_guidewith topicmotion_graphics. Then usecreate_composition/edit_compositionand look at the result withrender_framesbefore saying it is done. - Clearing the timeline, broad deletes, unlocking tracks, deleting folders and anything that spends credits need the user's yes. Claude Code shows Mocut's question right in the chat with Allow this time, Always allow or Don't allow; "Always allow" is saved for the project in Mocut (Settings → Permissions). Credits also follow the project's AI permission there. If the user declines, ask in chat before trying again.
- To change that permission, ask the user in your chat which they want (Always allow, Ask each time or Don't allow), then call
set_generation_permission. Ask each time and Don't allow are saved at once; Always allow is saved after the user confirms it in Mocut's own question. - Long calls return a
jobId: follow it withwait_for_job. - With a built-in browser, work in your own editor window beside the chat (in the Claude desktop app, the Browser pane rather than Chrome):
get_editor_statereturns its link aseditorUrl. - Before a multi-step change call
agent_statuswithworkingand a short label, anddonewhen you finish: the user's timeline stays locked while you work and shows your label. Astopped_by_useranswer means the user pressed Stop; ask before editing again. - To use a file from the user's computer:
create_media_upload, run the returned command, thenimport_media. The file goes to the user's Mocut Cloud storage. On the Free plan there is no cloud storage, so ask the user to drag the file into the editor instead. - If a tool says the editor is closed, outdated or not allowed, ask the user to open the editor, reload it, or switch on "Allow connected agents".
Without a terminal
In the Claude app or on claude.ai: open Settings → Connectors, choose Add custom connector, name it Mocut, paste https://mcp.mocut.app/mcp, click Connect and then Allow on the Mocut page. It works in Claude chats and in Claude Code in the desktop app.
Troubleshooting
- "Needs authentication": run
claude mcp login mocutagain, or in Claude Code type/mcp, choose mocut and Authenticate. - Disconnect: Account menu → Connected agents → Disconnect, or
claude mcp remove mocut.
Using Codex instead? See mocut.app/codex.