blender-control-mcp
Related Servers
Alternatives to blender-control-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables secure, local automation of Blender through typed MCP tools for scene, modeling, material, animation, rendering, and file workflows via an authenticated loopback bridge.173MIT
- AlicenseBqualityBmaintenanceEnables AI clients to control Blender through its official MCP add-on: running arbitrary bpy code or background CLI jobs, auditing scenes and blend files, searching Blender API and manual docs, capturing screenshots and renders, and searching or importing free Poly Haven models, HDRIs and textures at real-world scale. All 28 tools are served over one stdio connection to a single Blender instance.28GPL 3.0
- AlicenseAqualityDmaintenanceMCP 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
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to control Blender for modeling, materials, animation, physics, rendering, scene inspection, documentation search, and asset/generation service integration. It exposes a stdio endpoint with many Blender operations for creating and editing 3D content.AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceWindows-optimized MCP server that enables control of Blender 4.0+ through 21+ tools for scene management, object manipulation, and asset downloads from PolyHaven, Sketchfab, Hyper3D, and Hunyuan3D.16MIT
- AlicenseNot gradedqualityBmaintenanceConnects an AI agent to Blender 5.2 LTS over stdio, letting it read the scene hierarchy, create and transform primitive meshes, assign Principled BSDF materials, delete objects, save .blend files, and run raw bpy scripts through 12 tools. A two-process socket bridge keeps bpy calls on Blender's main thread, so no pip packages or admin rights are needed inside Blender.MIT
TDQS
Scored across 7 tools
Each tool addresses a distinct resource and action. Read-only tools (scene.inspect, material.list) are clearly separated from write operations (apply_material, transform, add_modifier, set_smooth_shading, export), and no two tools overlap in purpose. An agent could select the correct tool without ambiguity.
Tools follow a consistent <domain>.<action> pattern using dots (e.g., scene.inspect, asset.transform), but action verbs vary in style (e.g., 'apply_material' vs 'transform' vs 'export'). This is a minor inconsistency, but the pattern is predictable and readable.
With 7 tools, the server is well-scoped for asset inspection, material editing, transformations, modifiers, shading, and export. Each tool serves a clear purpose without redundancy or bloat, fitting comfortably in the ideal 3-15 range.
The surface covers common asset editing workflows (inspect, modify, export), but lacks removal operations such as deleting objects, removing modifiers, or changing material assignments. These gaps could cause dead ends in more complex pipelines, though core workflows are functional.