blender-research-mcp
Related Servers
Alternatives to blender-research-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP hosts and coding agents to model, inspect, measure, and deliver real Blender scenes through 15 tools and 217 catalog operations, returning actual rendered images after key edits. Works against a live Blender GUI via addon or a persistent headless worker, producing editable .blend files, GLB exports, previews, and acceptance records.1BSD 3-Clause
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build models, import assets, animate scenes, render images, and save versioned projects through validated MCP tools backed by headless Blender, with a live browser viewer for inspection.GPL 3.0
- AlicenseBqualityCmaintenanceEnables natural language creation and refinement of Blender scenes through structured MCP tools, with persistent object identity, visual validation, and reversible edits.23MIT
- AlicenseNot gradedqualityCmaintenanceLets an AI engine drive a Blender instance the user runs themselves over stdio JSON-RPC, enabling scene inspection, viewport capture and picking, sandboxed code execution, and gated asset search/import and 3D generation. Telemetry is disabled before import, outbound tools are withheld until per-run network consent, and VRAM gating plus a surface-policy tool report what is live and what a station has cleared.Business Source 1.1
- AlicenseNot gradedqualityCmaintenanceEnables local Blender-based product modeling and photography by exposing project management, scene editing, rendering, image inspection, and asset publishing tools to MCP hosts like Claude Code, with versioned .blend revisions and PNG renders.GPL 3.0
- 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
TDQS
Scored across 42 tools
The hierarchical domain prefixes make most tools easy to distinguish, and inspect vs. action tools are generally clear. However, object.set overlaps with object.transform and object.visibility.set, while application.status and connection.ping have ambiguous boundaries.
Most tools follow a predictable lowercase dotted prefix.action or prefix.subdomain.action pattern. Minor inconsistencies exist: object.visibility.set places the verb last, while modifier.set_state, shape_key.set_value, and material.set_input use compound verb_noun actions.
42 tools far exceeds the 25+ threshold and feels heavy for even a broad Blender domain. Several status and inspection tools could be consolidated without losing capability.
The tool surface covers project, object, material, texture, image, lookdev, render, and transaction workflows with few dead ends. Obvious gaps include material/image deletion, collection management, and explicit object selection mutation.