A
licenseA
qualityB
maintenanceEnables AI agents to drive Blender 5.1+ for modeling, sculpting, mesh editing, scene management, and rendering through live Python execution.
26
1
MIT
YABlenderMCP
by dassey
Related Servers
Alternatives to YABlenderMCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to control Blender through 150+ tools across 24 modules, including modeling, materials, lighting, animation, rendering, mesh quality analysis, and visual feedback, plus expert prompts and goal-first workflow management.2092MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect and modify live Blender scenes, manage objects and materials, render images, retrieve PolyHaven assets, and send prompts to configurable local or OpenAI-compatible LLM backends.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, inspect and modify scenes, manage PolyHaven assets, render images, and route prompts through configurable local or OpenAI-compatible LLM backends.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, manage scene objects and materials, render images, fetch PolyHaven assets, and send prompts to configurable local or OpenAI-compatible LLM providers with runtime switching.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, manage scenes, objects, materials, and renders, download PolyHaven assets, and switch between multiple LLM backends at runtime.-
TDQS
A3.9/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct roles: one executes code, the other returns documentation. There is no functional overlap, and the guide tool's description explicitly frames itself as orientation material read before multi-step work.
Naming Consistency5/5
Both names follow the same snake_case verb_noun convention (execute_blender_code, get_usage_guide). Consistent and predictable.
Tool Count2/5
The surface is effectively a single operational tool plus a documentation blob, which is very thin for a domain as broad as Blender automation. The description of execute_blender_code references 'structured tools' and 'dedicated tools' that do not exist in this set, suggesting the surface is a stub rather than a complete offering.
Completeness3/5
Arbitrary Python execution is theoretically Turing-complete and covers any Blender operation, so no hard capability gap exists. However, the tool itself notes the user can disable Python code, after which 'only the structured tools work' — yet no structured tools are present, leaving a dead end with no fallback and no guardrailed high-level operations.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues