Ref2Blender MCP Server
Related Servers
Alternatives to Ref2Blender MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to build game assets in Blender by modeling, lighting, rendering previews to inspect and correct, validating against engine budgets, and exporting to GLB/FBX.126MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to model, texture, animate, inspect, and export game assets directly in Blender, with rendered previews and glTF read-back for Godot and three.js.28 PyPIApache 2.0
- AlicenseBqualityCmaintenanceEnables LLMs such as Claude to drive Blender through high-level tools for real-world-scale modeling, PBR texturing, lighting, rendering, rigging/animation, and UE5 game-asset baking and export. It also provides asset-library search, reference comparison, quality inspection, and import/export of common 3D file formats.58MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents and Blender users to generate game-ready art through a set of Blender tools covering concept image generation, image-to-3D mesh creation, mesh cleanup, PBR material assignment, greybox level layout, camera pathing and still or sequence rendering. Every action runs headless Blender, returns machine-readable JSON with pass/fail self-checks such as triangle budget, scale, pivot and clearance, so agents can verify and fix each step unattended.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered 3D content creation in Blender through natural language, including text-to-3D, image-to-3D, animation, rigging, rendering, and export.3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to generate game-ready 3D assets from reference images with PBR textures, and to retexture meshes the user already owns, while recording full provenance for every generated file.2013MIT
TDQS
Scored across 8 tools
Each tool has a distinct role: status check, code execution, validation, summary, rendering, clearing, and two export variants. The only mild overlap is between check_model and scene_summary (both report triangle counts/dimensions), and execute_blender_code also returns an object summary, but the descriptions frame these as validation vs. listing vs. escape hatch.
Seven of eight names follow a predictable snake_case verb_noun pattern (check_model, export_model, clear_model, render_views, execute_blender_code). The exceptions are blender_status and scene_summary, which are noun-first, but they remain readable and unambiguous.
Eight tools is well within the sweet spot for a Blender bridge server. Each tool earns its place: status, execution, validation, summary, render, clear, and two export scopes.
The lifecycle is covered end to end: connect (blender_status), build/modify (execute_blender_code), inspect (scene_summary, check_model), visualize (render_views), export (export_model, export_all_assets), and reset (clear_model). The code-execution tool serves as a general escape hatch for any missing operations.