A
licenseNot graded
qualityB
maintenanceConnects Blender to LLMs, enabling prompt-driven 3D modeling, scene creation, and manipulation through natural language.
MIT
mcp-for-blender
by nludd25
Related Servers
Alternatives to mcp-for-blender
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to control Blender 3D software through natural language, with tools for modeling, materials, animation, rendering, and rigging.3810MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered 3D content creation in Blender through natural language, including text-to-3D, image-to-3D, animation, rigging, rendering, and export.2MIT
- FlicenseNot gradedqualityCmaintenanceConnects AI assistants to Blender 3D for natural language 3D modeling, scene inspection, material creation, and rendering.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create, inspect, and animate 3D scenes in Blender through natural language and structured tool calls.6MIT
- FlicenseNot gradedqualityNot gradedmaintenanceConnects AI assistants to Blender for controlling 3D modeling operations through natural language, enabling creation of objects, applying textures and materials, scene management, and transformations with optimized token efficiency.-
TDQS
A3.7/5.0
Scored across 31 tools
Disambiguation4/5
Tools are mostly distinct, with clear purposes per resource and action. There is slight overlap between bpy_api_lookup and describe_node_type (both are reference lookups), and the six get_*_status tools are repetitive but provider-specific. Overall, an agent can reliably select the right tool.
Naming Consistency4/5
Most tools follow a verb_noun snake_case pattern (get_*, search_*, download_*, generate_*, poll_*, import_*). Minor deviations like bpy_api_lookup and record_trajectory_feedback break the pattern, but the convention is still predictable and readable.
Tool Count3/5
31 tools is on the high side, but the server covers a broad scope: multiple asset libraries (Polyhaven, Sketchfab, Polypizza), AI generation (Hyper3D, Hunyuan3D), export, telemetry, and scene management. Each tool earns its place, though the count is heavier than ideal and could be streamlined by consolidating status checkers.
Completeness4/5
The surface covers scene inspection, code execution, API reference, asset search/download, AI generation with polling, export, telemetry, and feedback. Explicit object manipulation is missing but is covered via execute_blender_code. Minor gaps like direct material editing exist, but overall the domain is well covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues