🧠[Guide]Claude for 3D design

🔥🔥🔥 Blender MCP full guide

Step 1: Install the prerequisites

The Blender MCP installation requires several development tools that typical users may not have installed. Following the process precisely is critical, deviating from it frequently results in connection failures or missing dependencies.

For Windows:

• Python 3.10+: Install via WinGet with winget install python.python.3 

• uv Package Manager: Open PowerShell and run powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex" 

• PATH Configuration: Ensure %USERPROFILE%\.local\bin is in your user PATH, then restart Claude Desktop

• Blender 3.0+: Download from https://www.blender.org/download/lts/

• Claude Desktop: Download for Windows 10+ from Anthropic's support site

For macOS:

• Python 3.10+: Download from python.org or install via Homebrew with brew install python 

• uv Package Manager: Install via Homebrew with brew install uv 

• Blender 3.0+: Download the LTS version

• Claude Desktop: Download for macOS 11+

Step 2: Configure Claude Desktop

The configuration process involves three distinct components that must be set up in sequence. Failure at any step prevents the integration from functioning.

• Edit Claude Desktop config: Go to Settings > Developer > Edit Config and add the MCP server JSON with the uvx command

• Download addon.py from the GitHub repository

• Install in Blender: Navigate to Edit > Preferences > Add-ons > Install

• Enable the Blender MCP addon by checking the checkbox next to "Interface: Blender MCP"

• Open Blender's 3D View sidebar (press N), locate the BlenderMCP tab, and click "Connect to Claude"

• Fully quit and restart Claude Desktop. Verify the hammer icon appears indicating MCP tools are available

Step 3: Troubleshoot common issues

Based on community feedback, several installation issues commonly affect users:

• "Client Closed" error on Windows: UV not in PATH. Restart after adding PATH or use the full path to uvx.exe in your config

• First command fails: Known issue. Second and subsequent commands typically work. Just retry the command

• Connection timeout: Blender server not started. Click "Connect to Claude" in the Blender sidebar first

• MCP server not detected: Did not fully restart Claude Desktop. End the task completely and relaunch

• Port conflict (9876): Another instance running or port blocked by firewall. Check firewall settings

🔥🔥 🔥🔥 What Claude can actually do

The eight tools at Claude's disposal:

Once connected, Claude has access to eight specific tools for interacting with Blender:

1. get_scene_info: Retrieves current scene details including object count, names, types, and locations

2. get_object_info: Gets detailed information about a specific object in the scene.

3. get_viewport_screenshot: Captures visual state of the 3D viewport for validation, critical for spatial reasoning

4. execute_blender_code: Runs arbitrary Python code in Blender. Most powerful but potentially dangerous tool

5. search_polyhaven_assets: Searches Poly Haven for HDRIs, textures, and 3D models

6. download_polyhaven_asset: Downloads and imports assets from Poly Haven into the scene

7. search_sketchfab_models: Searches Sketchfab for downloadable 3D models

8. generate_hyper3d_model_via_text: Generates 3D models from text descriptions using Hyper3D Rodin AI

Where Claude excels (Excellent performance):

• Individual Object Creation: Creates primitives, applies transformations, and positions single objects accurately. Spheres, cubes, cylinders execute flawlessly

• Material Application: Applies colors, metallic properties, roughness, and emission. Node-based shader creation works reliably

• Python Script Generation: Generates complex procedural scripts using Blender's bpy API. Strong understanding of Blender's Python ecosystem

• Render Settings: Configures Cycles/EEVEE settings, resolution, samples, denoising. Camera positioning works accurately

  

Where Claude struggles (Significant limitations):

• Spatial Reasoning: Arranging multiple objects to make visual sense requires screenshot validation loops. Often places objects incorrectly relative to each other

• Visual Validation Loop: Takes screenshots to validate but corrections are inconsistent. Sometimes fixes issues, sometimes doesn't recognize problems or makes them worse

• Complex Scene Composition: Creates individual elements well but struggles with cohesive scene arrangement. Objects may overlap, float unexpectedly, or lack logical spatial relationships

• Scale and Proportion: Without explicit dimensions, objects may be incorrectly scaled relative to each other. Requires specific size parameters in prompts

🔥 The prompts that work (and the ones that don't)

Effective prompt patterns:

• "Add a sphere at location (0, 0, 2) with radius 1" — Specific coordinates and dimensions. No ambiguity

• "Apply a shiny gold metallic material to the selected object" — Clear material description with specific properties

• "Create a sun light at 45 degree angle with energy 5" — Quantified parameters for lighting

• "Configure Cycles render at 1920x1080 with 256 samples" — Specific technical parameters

• "Write a Python script to duplicate selected object 10 times in a circle" — Leverages Claude's strong scripting ability

Problematic prompt patterns:

• "Create a realistic kitchen" — Too vague. No dimensions, no object list, no style guidance

• "Make it look better" — Subjective. No actionable criteria for improvement

• "Arrange the furniture naturally" — Requires spatial/aesthetic judgment Claude lacks

• "Build a complete medieval village" — Scope too large. Will produce inconsistent, overlapping elements [R-line:218-219]

Where you'll need patience (or manual cleanup):

These scenarios may work but require significant iteration or produce inconsistent results:

• Complex Scenes: Creating detailed environments with many interrelated objects. Spatial relationships often incorrect. Better to build incrementally with validation

• Architectural Interiors: Rooms, buildings, structured spaces. Walls may not align, furniture placement inconsistent. Requires explicit coordinates and measurements

• Character/Organic Modeling: Claude cannot create detailed organic shapes or characters through primitives. Use Hyper3D integration for AI-generated models instead

• Precise Assemblies: Mechanical parts that must fit together exactly. Tolerances and alignment require manual verification and adjustment

🔥 Our gothic cathedral case study: 🔥

We created a complete Gothic cathedral interior with stained glass windows and volumetric light rays through natural language prompts alone.

• Total objects created: 254 (walls, columns, vaults, windows, pews, altar, candles, lights).

• Materials generated: 12 (stone, wood, 5 stained glass colors, candle wax, flame emission).

• Code execution steps: 14 separate Python script executions.

• Screenshot validations: 6 viewport screenshots for progress verification.

• Camera repositions: 4 attempts to achieve a good interior view.

What worked well: Systematic incremental approach (walls, then columns, then arches), complex procedural Python scripts for gothic arch curves and ribbed vault geometry, proper node-based shader networks for stained glass with emission, and correct Cycles render setup with volumetric settings.

What required iteration: Camera positioning (initially placed outside the cathedral), viewport perspective adjustments, and rose window component alignment.

Final assessment: For learning or rapid prototyping, this represents excellent value. For production work, manual refinement would be necessary.

🔥 Our Recommendations🔥

 1. Set Realistic Expectations: Understand that Claude is excellent at execution but limited in spatial reasoning and aesthetic judgment.

2. Use Specific Prompts: Provide exact coordinates, dimensions, and parameters whenever possible to minimize ambiguity.

3. Build Incrementally: Break complex scenes into discrete steps with validation between each.

4. Save Frequently: The arbitrary code execution capability means mistakes can be destructive. Maintain backups.

5. Leverage Strengths: Focus on use cases where Claude excels: scripting, material work, lighting, render config, and learning.

Who Should Use It

Blender Beginners: Highest value. Claude serves as an interactive tutor, executing operations while explaining them. Accelerates the learning curve significantly.

Technical Artists: High value for automation tasks, Python scripting, and batch operations. Leverages Claude's code generation strengths.

Rapid Prototypers: Good value for quick scene mockups and concept visualization. Results may require cleanup but save initial setup time.

Professional Artists: Limited value for production work. More useful as a utility for specific tasks than primary workflow tools.