EtchMotion includes a local MCP bridge. Codex or Claude can help define your channel style, prepare reviewed batches and safely edit individual Long-form scenes. Rendering stays on your PC.
Adds EtchMotion for your user account, ready for new Claude Code sessions.
claude mcp add --scope user etchmotion-studio -e ELECTRON_RUN_AS_NODE=1 -- "$env:LOCALAPPDATA\Programs\EtchMotion Studio\EtchMotion Studio.exe" "$env:LOCALAPPDATA\Programs\EtchMotion Studio\resources\integrations\etchmotion-studio\mcp\server.mjs"
1
Open EtchMotion
Wait until the bottom-left status says the local engine is online.
2
Run the command
Paste the copied line into PowerShell. Then start a new Codex or Claude task.
3
Ask normally
Try: "Check EtchMotion, help me define a channel style, then propose 20 reviewed videos."
These commands use the normal Windows install folder. If you chose a different folder, open Automation inside EtchMotion and use its exact Copy for Codex or Copy for Claude button.
What this unlocks
Plan widely. Review before rendering.
Your agent can inspect the live catalog, save and version a Channel Style, plan a six-month idea list, preview sources, create batches and recover queue jobs.
first promptafter connecting
Check EtchMotion Studio.
Help me define a recognisable Channel Style for a weekly nature quiz.
Show me two proof concepts first. After I approve one, plan 20 episodes and prepare the batch for review.
Clear boundaries
Useful access without handing over your channel.
INCLUDED IN 1.2
Read, prepare and revise
Compare all six engines and real recipes
Design, save and version Channel Styles
Plan concepts and export an upload-ready CSV
Create reviewed videos and batches
Add, patch, move and remove reviewed Long-form scenes
Inspect, cancel and retry queue jobs
NOT EXPOSED
Still your decision
No social publishing or account access
No project or media deletion
No hidden upload of source images
No claim that a licence clears likeness rights
No permanent automation token
No new renderer code disguised as a setting
EtchMotion Studio 1.2 includes the complete 29-tool revision-safe bridge. The app must remain open, and every local write still requires visible approval inside Studio.
If it does not connect
Three quick checks.
"EtchMotion Studio is not running"
Open the desktop app and wait until Automation says the local API is online. The connection file exists only while the app is running.
PowerShell says codex or claude is not recognised
The selected agent's command-line client is not installed or is not on PATH. Codex Desktop users can instead use the full plugin folder shown under Automation. Claude users should install Claude Code first.
The app was installed somewhere else
Open Automation in EtchMotion and click its exact Copy for Codex or Copy for Claude button. It uses the real path on your computer.