Skip to main content
Glama

Related Servers

Alternatives to cavalry-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      Enables natural language control of Cavalry animation software for creating layers, setting attributes, keyframing, rendering frames, and more via an MCP server.
      21
      31
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to inspect and edit Cavalry scenes by reading layers and connections, executing JavaScript, connecting nodes, changing Duplicator distributions, and rendering frames for visual feedback.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to control Cavalry, a procedural 2D motion graphics application, through natural language commands for creating and animating scenes.
      18
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables any MCP client to control After Effects, Premiere Pro, Photoshop and Illustrator through 182 native tools plus 500+ bundled community tools, covering layer/comp editing, rendering, export, plugin and extension discovery, and media downloads. Cross-app workflows move comps, layers, frames and MOGRTs between applications, while raw scripting escape hatches reach nearly any menu command or plugin action.
      182
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    cavalry_inspect is clearly the read path, while cavalry_run_script and cavalry_run_preset both execute code and could initially be confused. The descriptions resolve this (preset = one atomic parameterized rig build, script = general JS escape hatch), so boundaries are workable but not perfectly crisp.

    Naming Consistency4/5

    All three share a consistent cavalry_ prefix and use verb-style names (run_script, run_preset, inspect). The only minor deviation is that inspect has no object noun while the other two follow verb_noun, but the pattern remains readable.

    Tool Count4/5

    Three tools is on the lean side, but the design is deliberate: one general execution tool, one readback tool, one high-level preset builder. Each earns its place rather than being a thin, trivial surface.

    Completeness3/5

    The general script runner plus inspect covers most read/write workflows, but there is no discovery tool for available presets, _mg helper documentation, or broader scene/composition enumeration beyond selection and roots. Agents must guess at APIs, which will cause some dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues