Guides
Can Claude generate a 3D model from text? What it does alone, and what it needs a tool for
Claude can't output meshes alone, but it can script simple geometry or call a 3D generator through MCP. Which route fits which model, with prompts.
6 min read

Quick answer
Can Claude make 3D models?
On its own, the assistant writes code and text, not meshes, so it can only build simple shapes through scripts such as Blender Python, OpenSCAD or three.js. Connected to a 3D generation service through MCP, it can request a real textured model from a text prompt or image, then rig, animate or retexture it.
The short version
Claude is a language model. What comes out of it is text: sentences, and code. A 3D model is a file of vertices, faces, UVs and textures. So when you type "make me a 3D dragon", Claude has three options:
- Explain how you could make one. Useful, but not a model.
- Write code that builds a model when you run it.
- Call a tool that makes the model, through a connector.
Options 2 and 3 both end with a real file. They suit very different models.
Route 1: Claude writes code that builds geometry
Claude is strong at code, and several tools turn code into 3D:
- Blender Python (
bpy). Claude writes a script; you paste it into Blender's Scripting workspace and run it, or let a Blender MCP server run it for you. Good for primitives, arrays, procedural fences and shelves, modifiers, and scene automation. - OpenSCAD or CadQuery. Code-based CAD. Excellent for printable mechanical parts where dimensions matter: a 30 mm cable clip, a bracket with two M4 holes, a box with a sliding lid.
- three.js. Code that draws 3D in a browser. Handy for simple web scenes and prototypes.
What this route does well: exact sizes, repeatable parts, clean mechanical shapes, and anything you'd describe with numbers. What it does badly: organic forms. Ask for a dragon in Blender Python and you'll get spheres and cones arranged roughly like a dragon. That's not a failing you can prompt away; sculpted surfaces aren't something you write by hand as code.
A prompt that plays to this route's strengths:
"Write a Blender Python script that creates a low-poly wooden fence: 12 posts, 1.2 m tall, 2 m apart along X, with two horizontal rails between each pair. Use one material called M_Wood. Apply scale at the end."
More on this route: Claude for Blender Python scripts and Blender MCP with Claude.
Route 2: Claude calls a 3D generator
AI 3D generators make full meshes, with textures, from a text prompt or an image. Claude can't run them by itself, but with an MCP connector it can call one for you and hand back the file.
With Vi3W connected to Claude:
- You describe the model in chat.
- Claude turns that into a generation request and calls Vi3W.
- Vi3W generates the mesh and textures on its servers.
- Claude gives you the result, and you can keep going: Add bones, Make it move, New paint job, Clean shape, or download GLB, FBX, OBJ, STL, PLY or glTF.
This route does what Route 1 can't: creatures, characters, worn props, food, plants, anything with an organic surface. It's less precise about exact dimensions, so you scale the result afterwards. Setup takes a few minutes: Vi3W MCP in Claude.
A prompt for this route:
"Using Vi3W, make a stylised mossy stone lantern for a cosy fantasy game, chunky proportions, hand-painted look. Show me the result before doing anything else."

Which route for which model?
Pick by what the model is, not by which tool you like.
- Mechanical part with measurements (bracket, enclosure, clip, gear): Route 1, OpenSCAD or CadQuery.
- Modular kit pieces (walls, floor tiles, fences, shelves): Route 1, Blender Python.
- Scene automation (rename, place, align, export): Route 1, Blender MCP.
- Character or creature: Route 2, then Add bones and Make it move.
- Organic or worn prop (barrel, chest, statue, tree stump, food): Route 2.
- A model from a picture or sketch: Route 2. See Claude image to 3D.
- Printable figurine: Route 2, convert to STL, check in the slicer. See text to 3D print.
Many real jobs use both: generate the hero prop in Vi3W, then have Claude write the Blender script that places twenty copies on your level.
How to get a good result from either route
- Say what it's for. "For a mobile game" and "for a 3D print" lead to different answers on detail and file format.
- Give size and style. "40 cm tall, stylised, chunky" beats "a lantern".
- One object per request. "A lantern" works. "A lantern on a table in a tavern" asks for a scene, which generators don't make.
- Check before you continue. Ask Claude to show the result and wait.
There's a full prompt guide in how to prompt a chat for 3D models.
Claude in claude.ai, Claude Desktop and Claude Code
- claude.ai (browser): Route 2 works through a remote connector such as Vi3W. Route 1 works if you copy the code into Blender yourself.
- Claude Desktop: both routes, including local servers like Blender MCP that run code for you.
- Claude Code: both routes from the terminal. Particularly good for Route 1 projects with many scripts, and you can add skills that teach Claude your conventions.
A combined example: one prop, two routes
Say you're dressing a tavern for a game. The tables and benches are simple boxes with bevels, so Route 1 handles them: "Write a Blender script that makes a 2 m by 0.9 m tavern table with four square legs, a 5 cm bevel on the top edges and a material slot called M_Oak." The run of tankards, the carved bar sign and the barrel stack have organic, worn surfaces, so Route 2 handles those: "Using Vi3W, make a stylised pewter tankard with a dented rim, about 15 cm tall. Show me first." Once the generated props are downloaded, Claude can write one more script that imports them, scales each to its real size and places them on the tables. The code builds the parts that are measurements; the generator builds the parts that are surfaces.
What Claude can't do here
Claude doesn't see a 3D model the way you do. Even with a screenshot tool, it judges a picture of the scene, not the topology, the UVs or how the model deforms. It can't guarantee a generated model is watertight for printing, and it can't make a code-built shape look sculpted. It also can't decide whether a model fits your art direction. Treat it as a fast assistant that writes the code and makes the requests, and do the reviewing yourself.
Try it
Connect Vi3W to Claude with the setup guide, or make your first model in the Vi3W app and see what the generator produces before you bring Claude in.
Frequently asked questions
can claude make 3d models
Yes, in two ways. It can write code that builds geometry (Blender Python, OpenSCAD, three.js), which suits simple and mechanical shapes. Or it can call a 3D generator through an MCP connector, which suits detailed, textured models.
does claude generate 3d models
Not by itself. Claude's own output is text and code. A mesh file comes from code it writes and you run, or from a connected tool such as Vi3W's MCP server that does the generation.
can claude make 3d models for printing
For mechanical parts with exact dimensions, ask Claude for OpenSCAD or CadQuery code and export STL. For figurines and organic shapes, generate a model through a connected 3D tool and convert it to STL, then check it in your slicer.
is claude good at 3d modeling
It's good at the parts of 3D that are code and logic: scripts, scene automation, naming, exports and explaining tools. It's weak at sculpting organic detail through code, which is what generation tools are for.
Last reviewed

