F
licenseB
qualityC
maintenanceMCP server for driving Cavalry's 2D motion-graphics engine from LLMs, enabling scene creation and animation via natural language.
28
3
-
Cavalry MCP
Related Servers
Alternatives to Cavalry MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables AI assistants to control Cavalry, a procedural 2D motion graphics application, through natural language commands for creating and animating scenes.181-
- AlicenseBqualityBmaintenanceMCP server that lets AI assistants control Adobe After Effects via natural language, enabling composition and layer creation, animation, effects, presets, rendering, and arbitrary ExtendScript execution with Arabic/RTL support.50104 npmMIT
- FlicenseBqualityDmaintenanceEnables control of Adobe After Effects via natural language, allowing project manipulation, layer creation, animation, and rendering through MCP.72-
- AlicenseNot gradedqualityDmaintenanceEnables AI-assisted 3D scene manipulation in Cinema 4D via natural language, using an MCP server that communicates with a C4D plugin.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to control Cavalry motion graphics projects through its local JavaScript API, supporting scene and layer inspection, creation, editing, keyframing, expressions, saving, and rendering with validated structured results.MIT
TDQS
A3.7/5.0
Scored across 21 tools
Disambiguation5/5
Each tool targets a distinct operation (create, get, set, delete, etc.) with clear resource categories (layer, attribute, scene, composition). The catch-all run_script explicitly notes it's for cases where no specialized tool fits, reducing ambiguity. No two tools appear to serve the same purpose.
Naming Consistency4/5
All tools share the cavalry_ prefix and mostly use verb_noun (create_layer, get_attribute, save_scene). A few deviate: 'keyframe' and 'magic_easing' are noun-like commands rather than verb phrases, but the overall pattern is consistent enough.
Tool Count4/5
With 21 tools, the set is substantial but not bloated. It covers the primary workflow of creating, manipulating, animating, and rendering scenes. No redundant tools; each offers distinct functionality. Slightly heavy but appropriate for a professional design tool.
Completeness4/5
The tools cover scene lifecycle (open/save), layer CRUD, attribute reading/writing, animation (keyframes/easing), composition info, and rendering. Missing advanced features like undo or asset management, but the core workflows are fully supported. The run_script escape hatch fills niche gaps.
Maintenance
ActivityInactive
ResponsivenessUnresponsive