wassermanproductions/motion-previs-mcp

MCP server for Motion Previs Studio — extract camera + performance motion from reference footage via any MCP agent (Hermes, Claude, Codex). Zero dependencies.

About motion-previs-mcp

MCP (Model Context Protocol) stdio bridge for Motion Previs Studio — the open-source desktop app that turns real reference footage into AI-generator control packs. With this server connected, an AI agent can import a shot (local file or URL), trim the range, pick what to preserve (camera move, actor performance, object motion, or the full scene), run the analysis pipeline, watch its progress, export the bundle (depth passes, OpenPose skeleton video + keypoints, camera path, prompts), and send layers straight to the Blockout previs app.

1. Motion Previs Studio v4.1+ must be running. Get it from the app repo (build from source or use a release DMG). 2. On launch, the app starts a localhost-only control server on a random port and writes a discovery file to ~/.config/motion-previs/control.json (random bearer token, mode 0600, removed on quit). This bridge reads that file automatically — nothing to configure, no credentials to enter.

Add to ~/.hermes/config.yaml (or install from the Hermes MCP catalog once listed):

getstate · importfile · importurl · setrange · setmode · setsettings · runanalysis · exportpack · listbundle · sendtoblockout · screenshot

The agent workflow: importfile/importurl → setrange + setmode (cameraonly actormotion objectmotion fullscene) → runanalysis → poll getstate until analysis.status is done → exportpack → optionally sendtoblockout (reference / depth / aidepth / pose / openpose).

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/wassermanproductions--motion-previs-mcp.html)

Related MCP servers