BlenderMCP
Related Servers
Alternatives to BlenderMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects Blender to local LLMs through MCP, enabling AI-assisted 3D modeling, scene creation, and manipulation.1MIT
- AlicenseAqualityCmaintenanceConnects Blender 3D to AI assistants via the Model Context Protocol, enabling natural language driven 3D scene creation, manipulation, and rendering.15MIT
- AlicenseCqualityAmaintenanceEnables AI-powered control of Blender through natural language, allowing users to create, manipulate, and automate 3D scenes, objects, materials, animations, and more via Claude or other MCP clients.7144MIT
- AlicenseNot gradedqualityCmaintenanceConnects Blender to AI assistants through the Model Context Protocol, enabling direct AI control of 3D modeling, scene creation, and manipulation via natural language.MIT
- AlicenseBqualityDmaintenanceConnects Blender to Claude AI through the Model Context Protocol (MCP), enabling prompt-assisted 3D modeling, scene creation, and manipulation directly from Claude.17MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to control Blender via MCP tools for scene manipulation, material assignment, rendering, and Python script execution.131 PyPI26MIT
TDQS
Scored across 22 tools
Each tool targets a distinct resource and action. The integration-specific tools (PolyHaven, Sketchfab, Hyper3D, Hunyuan) are clearly separated by service, and the only potentially similar tools (generate_hunyuan3d_model vs generate_hyper3d_model_via_text/images) are distinguished by their backend and explicit naming.
All tools follow a consistent verb_noun snake_case pattern (e.g., get_scene_info, download_polyhaven_asset, poll_rodin_job_status). There are no mixed conventions or ambiguous verb styles, making the tool surface highly predictable.
At 22 tools, the set is slightly larger than the typical 3-15 range, but the server covers multiple distinct integrations (Blender core, PolyHaven, Sketchfab, Hyper3D, Hunyuan). Each tool contributes to a specific function, so the count is justified despite feeling heavy.
Core Blender operations (scene info, object info, screenshot, code execution) are well covered. Asset libraries and generation services have search/download/generate/poll/import workflows, but there are minor gaps such as lack of HDRI world application, no listing of downloaded assets, and no ability to edit objects beyond code execution. These are workaroundable via execute_blender_code.