A
licenseB
qualityD
maintenanceEnables prompt-driven scene generation for computer animation using a JSON-serializable scene model and physics simulation backend.
25
Apache 2.0
chuk-mcp-stage
by chrishayuk
Related Servers
Alternatives to chuk-mcp-stage
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConverts natural language prompts into 3D scenes and generates React Three Fiber code for web and ad applications.7,262 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.3314 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.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to model, sculpt, rig, animate and bake particle effects by editing a semantic scene document, with built-in software rendering, measurable critics that flag floating or broken geometry, and game-ready glTF export. It exposes templates, atomic edit batches, motion and effect previews, undo history, and no GPU, browser, or Blender required.23 npmApache 2.0
- FlicenseNot gradedqualityFmaintenanceOrchestrates Rive animations by enabling discovery, integration, and composition across frameworks like React and Vue, with code generation and multi-backend storage.5-
TDQS
A4.1/5.0
Scored across 9 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues