This Blender MCP case spells out the creative direction, asset list, rendering views, and video deliverables in one go. It is suitable as a starting prompt for a “large-scale creative prototype,” but a one-shot visual demo should not be treated as a shippable finished product.
Suitable tasks: Blender scene prototyping, game-world region sketches, and creative exploration where the model is expected to decide on assets and composition autonomously.
Unsuitable tasks: Final projects that require asset quality, layout, physical correctness, and production maintainability; the original post’s comments explicitly acknowledge that the result is more like a visual demo.
Applicable model version: Claude Fable 5.1 (explicitly mentioned in the original post).
Applicable client, agent, or API: Claude client/Agent + Blender MCP; the author also used a custom skill to connect a local ComfyUI texture-generation model.
Recommended reasoning tier and parameters: The original post does not disclose an effort setting or API parameters; the public data is approximately 400k tokens, 20–25 minutes, and a 20× subscription. These figures cannot be used to infer a generalizable cost.
The complete prompt published by the author in the comments (original post and comments):
can you generate me quite a large zoomed out diorama of a "world of warcraft style region".
load all your relevant entry blender skills etc. and you can just go ham here and do whatever you like.
for theming let's do something along the lines of 2 opposing forces/designs, fantastical.
You'll obviously need to generate a lot of assets here, terrain, trees, textures, etc.... This is quite a big job.
When it's done, take a couple of quick aerial shots like a diorama, then a 30-60s video running through the POIs.
I won't be giving you any guidance, so go ham!
More production-ready rewrite (retaining the case’s intent while adding acceptance boundaries):
Using the loaded Blender-related skills and Blender MCP, first build a large-scale, zoomed-out aerial prototype of a fantastical region.
Theme: two opposing forces/design languages. Plan the terrain, vegetation, buildings, roads, materials, and points of interest for each, and keep the visual rules consistent.
First output an asset list, scene zones, and verifiable acceptance criteria, then generate in stages. After each stage, check object naming, scale, cameras, and renderability.
When complete, output:
1. Two aerial images resembling a miniature diorama;
2. A 30–60-second video camera path passing through the main points of interest;
3. A list of completed items, items needing fixes, and known visual defects.
If a tool or local texture service is unavailable, clearly mark the fallback plan instead of pretending the task is complete.Environment: Fable 5.1, Blender MCP; the author also used a custom skill to connect a local ComfyUI and a lightweight image model to generate textures.
Input: The single-round creative prompt above; the author said they provided no further guidance.
Output: A visual prototype of an approximately 1 km × 1 km “WoW-style region,” containing terrain, trees, textures, and many other assets, along with aerial shots and a 30–60-second video.
Resources: The author gave approximately 400k tokens and 20–25 minutes in the comments; they used a 20× subscription, so no generalizable dollar cost was disclosed.
Review: The author acknowledged in the comments that individual asset quality was poor and that the overall result was better suited to a fun experiment; using it in a project requires checking each asset and reworking it in stages.
Original post: The author said they were experimenting with Blender MCP and local image AI, and that Fable 5.1 generated a relatively large region in one shot.
The author’s comments included the complete prompt and specified a “World of Warcraft-style region,” two opposing designs, assets/terrain/trees/textures, aerial shots, and a 30–60-second POI walkthrough video.
The author’s comments gave the resource figures: approximately 400k tokens, 20–25 minutes, and a 20× subscription; these are observations from that run, not an official billing benchmark.
The counterexample in the comments is important: The author acknowledged that many individual assets were very poor, and that the whole looked good at a quick glance but fell apart on close inspection. This limits how far the case can be reused.
“WoW-style” is suitable only as an example of a non-commercial visual direction; before production use, check IP, asset provenance, and similarity risks.
A single large prompt can produce a visual prototype, but it does not amount to a playable game world; production projects should be split into planning, asset, layout, checking, and rendering stages.
MCP, the Blender version, the local texture service, and the subscription multiplier all affect the result. Reproduction must record the specific versions and tool state.
The original post does not disclose complete logs, the final project file, or per-asset quality scores, so “one shot” cannot be treated as a controlled benchmark.
“Was just tinkering with what the Blender MCP could do.”
“The individual assets are TRASH.” (the author’s self-assessment of quality in the comments)
Claude Fable 5.1