An animation studio on one laptop: first let Claude write the storyboard, then head into Blender
Opus 5.5, Blender, Remotion, and MCP are assembled into a single-machine character animation pipeline. The process starts with a director's brief and ends with an editable project and an MP4. Some people are already selling finished results; what is more worth seeing is how it is broken down into six steps.
le0xet posted a tweet showing how to make complete character animation on a single laptop using Opus 5.5, Blender, and Remotion. The tweet also mentions that people are already selling these finished videos.
This tweet breaks character animation into a reproducible local pipeline: Claude first writes the director's brief, Blender handles scenes, rigging, and keyframes, Poly Haven supplies CC0 materials and HDRIs, Remotion does compositing, and FFmpeg delivers the MP4. Every step leaves behind an editable project.
The trouble with traditional character animation is the long process. Modeling, rigging, blocking, facial expressions, lighting, camera, rendering, and editing are scattered across different tools, and one person can easily get stuck on wiring things together and redoing work. le0xet's approach puts an LLM in the role of director and technical artist, letting Claude read the scene, write Blender Python, and then send commands into Blender through MCP.
MCP is the Model Context Protocol, which here can be understood as a socket between Claude and Blender. MCP for Blender is a third-party integration, not an official Blender project. It lets Claude execute Blender Python and also see the viewport, camera, multi-angle views, and animation frames. The project author is Siddharth.
The six-step process is as follows.
01 / First give Claude a director's brief
One character, one scene, one visual joke. Before there is any object in the scene, write down the shots, expressions, camera movement, and final poses clearly. This order saves rework later. A commenter in the replies suggested locking the shot list and duration first, rendering a rough cut as early as possible, then looking at camera and pacing problems, and only polishing materials and lighting at the end.
02 / Connect Claude Code to Blender
Use MCP for Blender to connect Blender to Claude Code. The commands are short:
claude mcp add blender uvx mcp-for-blender
uvx mcp-for-blender install-addon
Then enable the add-on in Blender and start its server. The project is at MCP for Blender. Note that by default this tool can execute arbitrary Blender Python code. Save your project before using it, and break complex operations into small steps.
03 / Build the scene and animate
Blender handles the scene, rigging, keyframes, and character motion. First block out the keyboard and character, then work on the walk, eyes, glass, and close-ups. Blender's animation tools include pose editing, NLA, forward and inverse kinematics, and sound synchronization; the rigging side includes automatic skinning, weight painting, and bone layers. Specific features are on the Blender animation page.
04 / Light the world
Poly Haven provides CC0 HDRIs, textures, and models. Set up a reflective environment for the glass so the character remains readable against the background. Poly Haven assets can be used commercially and do not require attribution. Downloads happen on the main thread, and large files may briefly freeze the Blender interface; choose resolution according to the shot distance, and don't max it out from the start.
05 / Composite the final video
Remotion assembles the render sequence, titles, and audio into a reusable composition. You can add the official agent guide to the project:
npx skills add remotion-dev/skills
The docs are at Remotion AI skills. The value of this step is reuse. After the video is done, the project still exists, so the next time you change a shot you don't have to start from zero.
06 / Export and check
FFmpeg produces the delivery file. Watch the actual MP4, check the audio, and keep the editable scene and project files. Don't just look at the preview. The export check is the step most like a real production floor in the whole pipeline, and it is also the easiest to skip.
The whole loop is: brief -> scene -> character -> materials -> light -> camera -> preview -> render -> edit -> export.
The value of this combination is very practical: it frees one person from pipeline wiring and lets directorial judgment appear earlier. Some people are already selling outputs, but don't rush to treat a demo as production capacity. Being able to reliably reproduce a video and keep an editable project is what this setup can actually leave behind.
References: le0xet's original tweet, the MCP for Blender repository, the Blender animation features page, the Poly Haven license page, and the Remotion documentation.
发布时间: 2026-10-25 17:46