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
MIT
blender-mcp
by Mishaadevv
Related Servers
Alternatives to blender-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceEnables 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.209MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to fully control Blender through 50+ tools for 3D modeling, animation, materials, and scene management via HTTP endpoints.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create, inspect, and animate 3D scenes in Blender through natural language and structured tool calls.6MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to control Blender 3D software through natural language, with tools for modeling, materials, animation, rendering, and rigging.3812MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect and drive Blender scenes directly, either through a live editor bridge on port 8190 or automatically via headless background CLI when Blender is closed. Provides token-efficient tools for scene outlining, object creation and modification, modifiers, materials, rendering, asset export, and arbitrary bpy script execution.-
TDQS
B3.1/5.0
Scored across 122 tools
Disambiguation2/5
Many tools occupy nearly identical territory: blender_import_asset/blender_import_model and blender_export_asset/blender_export_model describe essentially the same operations, and validation is split across blender_validate, blender_find_problems, blender_auto_validate, and blender_diagnose. There are also multiple UV tools and several material-creation paths, forcing an agent to parse fine-print differences to avoid misselection.
Naming Consistency3/5
The blender_ prefix and snake_case style are consistent, and most tools use a verb_noun pattern. However, many domain-noun tools like blender_uv, blender_rig, blender_physics, blender_curves, blender_modifiers, and blender_scene_ops break the verb convention, and vague verbs like manage plus near-duplicate import/export naming weaken predictability.
Tool Count1/5
122 tools is an extreme mismatch, far beyond the 50+ threshold for incoherence. While Blender is a large domain, many tools are bundles or near-duplicates that could be consolidated into a much smaller, more navigable set without losing real capability.
Completeness4/5
The tool surface covers nearly every major Blender workflow: objects, meshes, materials, textures, UVs, animation, physics, rendering, import/export, and asset libraries, with an explicit Python escape hatch for anything missing. Minor gaps remain as dedicated operations, such as deleting materials/images, adding constraints, or editing vertex groups, but these are workable via blender_run_operator or blender_execute_python.
Maintenance
ActivityMaintained
ResponsivenessNo issues