MCP tools
The genmotion MCP server gives Claude Code, Codex and Cursor tools to create projects, add scenes, check them, capture frames as images and render MP4.
npx genmotion mcp runs a Model Context Protocol server over stdio. It gives agents tools instead of more text to read. Projects made with init register it already; see Connect your agent to add it anywhere else.
Tools#
| Tool | What it does |
|---|---|
project_overview | Size, fps, engine, every scene with its file, start frame and length, audio and assets. Agents call this first |
create_project | Create a project folder with a starter scene and agent files, optionally from a template |
add_scene | Create a scene file and register it in project.json |
validate_scene | Compile one scene and check the determinism rules. Fast, no browser |
check_project | The full check: manifest, every scene compiled, and a headless render of each scene's first, middle and last frame |
capture_frames | Render frames and return them as images the agent can look at. Times like 1.5s, 45, 500ms, 60% |
render_video | Render the video to a file, exports/<name>.mp4 by default |
save_asset | Download a remote image, audio, video, font or 3D model into assets/ (up to 25 MB) |
add_package | Install a browser-safe npm package, with lifecycle scripts disabled |
search_skills | Find the skill that owns this kind of video, from the user's own words |
get_skill | Read a skill and, when needed, one of its reference files |
get_guide | Reference on demand: three (scene authoring), workflow, cli |
list_templates | The template catalog, for create_project |
Every tool takes an optional dir when the server didn't start in the project folder.
How an agent uses them#
A typical session:
project_overviewto learn the project.search_skillsandget_skillto pick how this video is made.add_scenefor each scene, then edits the files.check_projectandcapture_framesafter each change, and looks at the frames.render_videoat the end, or when you ask.