Building the Claude Mascot with Claude Code and the Blender MCP
An honesty report. Claude Code, driving a live Blender through the Blender MCP, builds the Claude mascot as a 3D model and rigs it for animation, and this film shows what worked, what broke, and what could not be proved. Every step was run for real, in a throwaway Blender profile: a written brief, a plan, nine parts…
Building the Claude Mascot with Claude Code and the Blender MCP
An honesty report. Claude Code, driving a live Blender through the Blender MCP, builds the Claude mascot as a 3D model and rigs it for animation, and this film shows what worked, what broke, and what could not be proved. Every step was run for real, in a throwaway Blender profile: a written brief, a plan, nine parts built in nine tool calls in under two minutes, and then a script that is not Claude reading the live scene back. It also shows the failures: grey renders, a correct pixel reading that Claude talked itself out of, a rig that moved every part 4 cm, and a rig built by parenting rather than skinning. Godot imports it, and moving one bone moves only its part.
One run only: a headless Claude Code session (not a person at a terminal), one A. I. model (reported as claude-sonnet-4-6), one Mac, MCP for Blender 2.1.9. The exact default-scope claude mcp add command was not run, because it would have changed the author's global Claude Code settings.
Chapters 0:00 The shortcut, and why this film checks instead 0:14 Terms in this lecture 0:33 I. The job: the mascot, nine boxes, and the brief 1:35 II. Connect Claude to Blender: uv, the add-on, the open port, claude mcp add 3:13 III. Plan, then build: one part per call, then an independent read-back 4:30 IV. What went wrong: grey renders, a wrong pixel, a 4 cm jump 5:55 V. The rig and the proof: bones, the glb, Godot 7:03 VI. What it can and can't do 7:57 Recap 8:17 Your turn
Your turn. Paste this into Claude: I want a simple three-D character built in Blender through the M C P. First write me a brief: each part as a box with its size and centre in metres, the origin at the feet, two colours, a triangle budget, and three predicted failures, each with the check that would catch it. Wait for my approval. Then build one part per call, printing each part's location, size, rotation and scale. Finally, tell me what you could not verify. Then check two things yourself: can a script that is not Claude confirm every number against the brief? And does the picture look right to you, with one pixel measured outside Blender?
Sources A recorded run on 6 October 2026: five headless Claude Code prompts against a live Blender 5.1.2 through MCP for Blender 2.1.9 (github.com/ahujasid/mcp-for-blender), with independent read-backs and a Godot 4.7.2 import. The Blender window screenshots were taken by a script. The mascot's proportions come from its 2D animation source.
Made with the brutalist.art toolkit: Manim, Remotion and Kokoro, free and local. Narration is synthetic (Liam, in for Bear). An independent educational film, not an official Blender, Godot or Anthropic publication.
What this video covers
- 0:00 — The shortcut, and why this film checks instead
- 0:14 — Terms in this lecture
- 0:33 — I. The job: the mascot, nine boxes, and the brief
- 1:35 — II. Connect Claude to Blender: uv, the add-on, the open port, claude mcp add
- 3:13 — III. Plan, then build: one part per call, then an independent read-back
- 4:30 — IV. What went wrong: grey renders, a wrong pixel, a 4 cm jump
- 5:55 — V. The rig and the proof: bones, the glb, Godot
- 7:03 — VI. What it can and can't do
- 7:57 — Recap
- 8:17 — Your turn
