mcp-blender-server
Related Servers
Alternatives to mcp-blender-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to control Blender through natural language for 3D scene creation, animation, and rendering. It provides over 550 actions and direct Python execution via a bridge to a live local Blender session.6MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to control Blender's 3D workflow via an embedded MCP server.328 PyPI36MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants like Codex or ChatGPT to inspect and control a local Blender scene, including creating objects, editing materials, setting cameras and lights, rendering previews, and saving safe copies of .blend files.MIT
- AlicenseAqualityDmaintenanceMCP server for AI-assisted Blender automation, providing layered tools for perception, declarative and imperative writing, and fallback operations.2959 PyPI5MIT
- FlicenseBqualityDmaintenanceMCP server that controls Blender via HTTP bridge, enabling 3D modeling, animation, and export operations from Cursor agent.321-
- AlicenseAqualityCmaintenanceMCP server for Blender that connects to the official Blender Lab add-on, exposing 27 tools for scene manipulation, object editing, materials, rendering, and Python execution through the add-on's actual wire protocol.271MIT
TDQS
Scored across 22 tools
Most tools have distinct purposes: downloading from different sources, generating via different services, checking status, etc. Some potential confusion between generation tools (Hunyuan vs Hyper3D) and between search/download for different asset stores, but descriptions clarify the differences.
All tools follow a consistent verb_noun pattern in snake_case (e.g., download_polyhaven_asset, generate_hyper3d_model_via_text). No mixing of styles or irregular naming.
22 tools is on the high side, bordering on heavy for a single server, but still manageable given the integration of multiple asset services and generation pipelines. It exceeds the typical 3-15 range but doesn't feel excessive for the scope.
Covers the full lifecycle for asset integration: search, preview, download, generation, status polling, import, and texture application. Missing object manipulation, creation of primitives, or export, which are beyond its specialized focus.