Cavalry MCP
Related Servers
Alternatives to Cavalry MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to operate Adobe After Effects with the dexterity of an editor: reading projects, creating and rigging layers, setting real velocity curves, animating text, building native SVG-based shapes, applying effects, expressions, masks, and viewing render snapshots to verify results.1716 npm1MIT
- AlicenseBqualityCmaintenanceEnables AI clients to create and edit Adobe After Effects compositions, add and animate layers, apply effects, and view sampled frames to verify the rendered result.11MIT
- AlicenseAqualityAmaintenanceEnables an AI agent to drive a running Adobe After Effects, inspecting projects and editing comps, layers, effects, keyframes, text, masks, expressions, and rendered frames through natural language. It provides a small tool surface with dry-run validation and undo-grouped operations for safe autonomous use.12241 npm1-
- AlicenseCqualityCmaintenanceEnables AI assistants and other applications to control Adobe After Effects through a standardized protocol, including composition creation, layer and mask management, keyframe and expression animation, and batch property edits.1357 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to control Adobe After Effects to create videos programmatically, with commands for comps, layers, effects, and rendering.8 npm23MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude Code, Claude Desktop, and VS Code to build and edit inside a running Adobe After Effects, covering comps, layers, keyframes, effects, text animators, markers, and renders. It supports batched tool calls with single-step undo, frame previews for self-verification, reusable style tokens, and four one-call studio rigs.MIT
TDQS
Scored across 29 tools
Each tool targets a distinct resource and action, with clear separation between attribute reads (get_attributes), path discovery (list_attributes), and writes (set_attributes vs set_keyframes). The only minor overlap is create_layer vs create_primitive, since primitives are a subset of layers, but the descriptions make the boundary reasonably clear.
Every tool uses the same cavalry_ prefix followed by a consistent verb_noun pattern (e.g. cavalry_set_attributes, cavalry_delete_layers, cavalry_create_layer). No mixed casing or verb-style deviations.
With 29 tools the surface is on the heavy side, and several could be folded together (e.g. create_primitive into create_layer). However, the domain—scene, layer, attribute, keyframe, and connection management for a motion graphics app—genuinely needs broad coverage, so it is borderline rather than excessive.
The set covers layer lifecycle (create/duplicate/rename/delete), attributes, keyframes, connections, parenting, selection, scene open/save, playback, frame control, and rendering. Minor gaps exist, such as creating a fresh scene or exporting video/image sequences, but core workflows are fully supported.