A
licenseB
qualityA
maintenanceEnables AI agents to drive a live Blender session for modeling, shading, lighting, rendering, and scene manipulation, returning rendered images for visual feedback.
4
122
MIT
rogue-blender-mcp
Related Servers
Alternatives to rogue-blender-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, manage scenes, objects, materials, and renders, download PolyHaven assets, and switch between multiple LLM backends at runtime.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session with scene/object manipulation, rendering, PolyHaven asset tools, and runtime-switchable LLM provider backends.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, inspect and modify scenes, manage PolyHaven assets, render images, and route prompts through configurable local or OpenAI-compatible LLM backends.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, manage scene objects and materials, render images, fetch PolyHaven assets, and send prompts to configurable local or OpenAI-compatible LLM providers with runtime switching.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect and modify live Blender scenes, manage objects and materials, render images, retrieve PolyHaven assets, and send prompts to configurable local or OpenAI-compatible LLM backends.-
TDQS
A3.6/5.0
Scored across 26 tools
Disambiguation4/5
Most tools have clearly distinct targets: manual docs vs API docs, window vs area screenshots, object name vs data-block name, and interactive vs CLI execution. A few pairs are close, especially search_manual_docs and search_api_docs, but the names and first-line descriptions make the intended choice reasonably clear.
Naming Consistency5/5
All tool names are snake_case and follow a predictable verb-first pattern: search_*, get_*, jump_to_*, execute_*, render_*. The get_blendfile_summary_* family and the repeated _for_cli suffix make parallel interactive/CLI tools easy to recognize.
Tool Count2/5
At 26 tools, the surface is too heavy, and much of the count comes from every get_blendfile_summary_* tool having a _for_cli twin that duplicates the same logical operation. Consolidating the CLI variants into a mode parameter would make the set much tighter.
Completeness4/5
The domain is clearly Blender inspection, navigation, rendering, and documentation, and those workflows are well covered: object summaries, blend-file health checks, viewport jumps, screenshots, rendering, and doc search. The main gap is a lack of direct high-level object or file mutation tools, but execute_blender_code provides an escape hatch for arbitrary bpy operations.
Maintenance
ActivitySlowing
ResponsivenessNo issues