AI Skill Report Card

Modeling 3D with Blender MCP

A-84·Aug 30, 2026·Source: Web
YAML
--- name: modeling-3d-with-blender-mcp description: Generates industrial-ready 3D models (vehicles, products, mechanical parts) inside Blender by driving the Blender MCP tool programmatically, using web research to gather real-world reference data (dimensions, brand/model specs, design cues) before modeling. Use when a user requests a 3D model of a specific vehicle, brand, product, or industrial object, especially newly released or real-world items that require research-backed accuracy. ---
14 / 15

When the user says something like "I need a 3D model of a [Brand] [Model] SUV" or "generate a 3D model of [newly released product]":

  1. Research the subject online (specs, dimensions, reference images, silhouette, proportions).
  2. Write a Model Brief (dimensions, key design features, reference image links, phase plan).
  3. Execute the build in Blender via MCP, phase by phase, checking geometry after each phase.
  4. Deliver: .blend file + render preview + brief summary of what was modeled.
Python
# Example MCP call pattern (pseudo, adapt to actual blender-mcp tool signature) blender_mcp.execute(code=""" import bpy bpy.ops.mesh.primitive_cube_add(size=2) obj = bpy.context.active_object obj.name = "SUV_Body_Blockout" obj.scale = (2.3, 4.6, 1.75) # width, length, height in meters from research brief """)

Never start modeling without a brief. Research first, model second.

Recommendation
Add a concrete example showing actual MCP script output for a full phase (e.g., Phase 2 base mesh code), not just the blockout pseudo-code, to strengthen examples with real input/output pairs.
15 / 15

Phase 0 — Brief Gathering (always first)

  • If user gives a brand + model (e.g., "Toyota Land Cruiser 2024" or "Tesla Cybertruck"): web-search for:
    • Official dimensions (length, width, height, wheelbase, ground clearance)
    • Reference images (front, side, rear, 3/4 view)
    • Distinct design language (grille shape, headlight style, body lines, proportions)
  • If user gives a generic request ("a SUV", "an industrial pump"): search for category-defining references and propose a design direction, confirm briefly with assumptions stated (don't block on approval — proceed with reasonable defaults, state them).
  • Summarize findings into a Model Brief:
    • Real-world dimensions (convert to meters for Blender units)
    • Key surfaces/features list
    • Reference image URLs
    • Phase plan (see below)

Phase Plan (standard for vehicles/industrial objects)

Progress:
- [ ] Phase 1: Blockout — primitive proxies at correct real-world scale/proportions
- [ ] Phase 2: Base Mesh — main body form via box modeling / mesh extrusion, correct silhouette from all views
- [ ] Phase 3: Detailing — panel lines, greenhouse, wheel arches, grille, lights, mirrors, handles
- [ ] Phase 4: Hard-surface refinement — bevels, edge creasing, subsurf-ready topology
- [ ] Phase 5: Wheels/undercarriage/mechanical subsystems (if applicable)
- [ ] Phase 6: UV unwrap + material/PBR shader setup
- [ ] Phase 7: Lighting + render pass for preview
- [ ] Phase 8: Export/cleanup (apply modifiers, check scale, naming, collections)

Execution rules per phase

  • Send one focused MCP script per phase — don't cram all geometry in one call.
  • After each phase, take a viewport screenshot / render via MCP and visually sanity-check proportions against reference.
  • Name every object/collection meaningfully (Body_Shell, Wheel_FL, Grille, Headlight_L) — never leave default Cube.001 names.
  • Keep real-world scale (meters) throughout; never model arbitrary unitless blockouts.
  • Use modifiers (Mirror, Bevel, Subdivision Surface, Solidify) instead of manual symmetric duplication.

Brand/Model-Specific Requests

  • Always research the specific trim/year if given.
  • If exact model can't be found (too new/no data), state the assumption ("no public specs yet, using closest predecessor + general segment proportions") and proceed — never stall.
  • Respect trademark/IP sensitivity: model in the style of, don't claim official licensed assets.
Recommendation
Include a 'bad output' example (e.g., wrong-scale blockout or default-named objects) to contrast against the good examples per the examples-quality criterion.
15 / 20

Example 1: Input: "I need a 3D model for a Ford Bronco Raptor, industrial ready" Output:

  • Brief: 4.8m L x 2.06m W x 1.9m H, boxy retro-modern SUV, round headlights, flared arches, visible tow hooks. Refs: [3 image URLs].
  • Phases executed 1→8 via MCP, screenshots after Phase 2 (silhouette match confirmed) and Phase 4 (panel detail).
  • Delivered: ford_bronco_raptor.blend, PBR materials (body paint, matte black trim, glass), turntable render, topology is quad-based and subsurf-clean.

Example 2: Input: "generate a 3D model for a newly released SUV" (no brand given) Output:

  • Research trending 2024/2025 SUV releases, pick most notable recent launch, state choice explicitly ("Using the [Model] since it was the most recent notable release found").
  • Proceed through full phase plan, deliver model + brief.
Recommendation
Clarify the actual blender-mcp tool signature/API expectations or note where to find it, since the pseudo-code is explicitly marked as an approximation.
  • Real-world scale always — convert imperial to metric if source specs are in feet/inches.
  • Reference images guide proportions and silhouette, not literal texture tracing — build clean topology.
  • Prefer box-modeling + modifiers over sculpting for industrial/hard-surface work (cleaner, more editable topology).
  • Keep an explicit object/collection hierarchy: Vehicle > Body, Wheels, Interior, Glass, Details.
  • Validate each phase visually before moving to the next — cheap to catch proportion errors early, expensive later.
  • State assumptions out loud in the brief rather than blocking with questions.
  • Don't skip the research/brief step and jump straight to primitives — leads to wrong proportions.
  • Don't model at arbitrary scale ("looks about right") — always use real dimensions.
  • Don't dump the entire model-build into one giant MCP script — phase it so failures are isolated and debuggable.
  • Don't leave default Blender object names — breaks downstream pipeline usability.
  • Don't over-detail before the silhouette/proportions are locked (Phase 2 gate before Phase 3).
  • Don't claim exact OEM-licensed accuracy — this is reference-inspired modeling, not reverse-engineered CAD.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
15/15
Examples
15/20
Completeness
17/20
Format
14/15
Conciseness
13/15