chuk-mcp-stage
Related Servers
Alternatives to chuk-mcp-stage
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables prompt-driven scene generation for computer animation using a JSON-serializable scene model and physics simulation backend.25Apache 2.0
- AlicenseNot gradedqualityDmaintenanceConverts natural language prompts into 3D scenes and generates React Three Fiber code for web and ad applications.10,151 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to control and manipulate live 3D scenes across frameworks like Three.js, A-Frame, and Babylon.js using a comprehensive set of object and environment tools. It features an integrated in-world chat system that allows for real-time scene modifications directly from within the 3D canvas.3332 npm3MIT
- FlicenseNot gradedqualityAmaintenanceAI-native video composition and VFX engine that exposes its capabilities as MCP tools, enabling AI agents to act as directors and create videos programmatically.-
- FlicenseNot gradedqualityFmaintenanceOrchestrates Rive animations by enabling discovery, integration, and composition across frameworks like React and Vue, with code generation and multi-backend storage.5-
- AlicenseNot gradedqualityAmaintenanceA batteries-included 3D engine for Three.js and Rapier that enables AI agents and humans to build, inspect, and control deterministic game simulations through a built-in Model Context Protocol (MCP) server.10 npmMIT
TDQS
Scored across 9 tools
Each tool targets a distinct aspect of 3D scene composition: objects, shots, physics binding, simulation baking, environment, export, and retrieval. No two tools have overlapping purposes.
All tools follow a consistent 'stage_verb_noun' pattern in snake_case, e.g., stage_add_object, stage_get_scene, stage_set_environment. The naming convention is uniform and predictable.
9 tools cover the essential operations for a 3D staging and export server without being overly numerous or sparse. The count is well-scoped for the domain.
The tools cover the primary workflow (create, add, bind, bake, export) and include getters. Minor gaps exist: no update/delete for objects or shots, and no scene deletion. However, these are manageable for most use cases.