Kimodo MCP
Related Servers
Alternatives to Kimodo MCP
No user-submitted related servers found.
Related Servers
- 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
- AlicenseBqualityDmaintenanceEnables LLMs to plan and stage editable Blender scene animations via a typed ShotSpec, with a safe stage/review/apply workflow, scene scanning, locomotion planning, and MCP integration for Codex/ChatGPT clients.17GPL 3.0
- AlicenseBqualityBmaintenanceEnables MCP clients to plan storyboards, write and lint ManimGX scenes, inspect layouts, render previews, review clips, and produce approved final 1080p animations.191MIT
- FlicenseBqualityBmaintenanceEnables guided 3D previsualization planning, camera and action audits, saved-scene inspection, and revision/gate tracking through a local Review Room and reusable articulated mannequin library. It also supports consent-based update checks, while scene creation, animation, and rendering remain in separate Blender tools.32-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control the Blockout previs desktop app for AI filmmaking, allowing staging of 3D worlds, character animation, camera framing, timeline control, and viewport screenshotting through MCP tools.7Apache 2.0
- AlicenseBqualityBmaintenanceEnables MCP clients such as Claude and Codex to drive Apple Creator Studio apps on macOS—including Pixelmator Pro, Keynote, Pages, Numbers, Compressor, Final Cut Pro, Motion, Logic Pro, and MainStage—plus headless Blender, Rive CLI, and Godot, entirely locally. It provides tools for app automation, UI accessibility, exports, transcoding, timeline creation, and headless creative and game workflows.38335 npm1MIT
TDQS
Scored across 37 tools
Most tools target distinct lifecycle stages, but several boundaries are subtle: generate_motion vs generate_animation, plan_animation vs revise_animation, and inspect_motion vs inspect_motion_frames vs analyze_motion_quality vs create_motion_review. Detailed descriptions help, but an agent could still misselect among these overlapping motion-generation and inspection tools.
Tool names consistently use snake_case and mostly follow a clear verb_noun pattern such as list_models, generate_motion, inspect_motion, prepare_blender_handoff, and execute_unreal_handoff. Minor exceptions like health_check are readable and do not disrupt the overall convention.
With 37 tools, the server is heavy for an agent-facing surface and exceeds the typical well-scoped range. The domain is complex, but multiple generation, inspection, review, export, and handoff variants make the set difficult to navigate as a whole.
The surface covers a broad lifecycle: planning, validation, generation, job management, inspection, export, review, comparison, character prep, and Blender/Unreal handoffs. Minor gaps exist around cleanup/deletion and broader character management, but core workflows are well covered.