Skip to main content
Glama
Sign In
Cavalry MCP Bridge

Cavalry MCP Bridge

by matthewobanla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Cavalry MCP Bridge

No user-submitted related servers found.

    Related Servers

    • Cavalry Bridge

      Jo-Serk
      A
      license
      Not graded
      quality
      C
      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

    • cavalry-mcp

      akspro9866-art
      A
      license
      B
      quality
      B
      maintenance
      Connects any MCP client to Cavalry animation software, enabling creation of layers, attribute editing, keyframe animation with Magic Easing, PNG frame rendering, and scene save/open. Every tool returns real data read back from the running scene, including layer IDs, attribute values, bounding boxes, and composition info.
      3
      MIT

    • ae-mcp

      maximejacquart
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      17
      18 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target clearly distinct operations: creation, attribute access, graph connections, timeline, playback, and rendering. However, `eval_expression` and `run_script` overlap in JS execution, and `render_queue` vs `add_to_render_queue` could cause minor confusion despite different purposes.

    Naming Consistency4/5

    All tools share the `cavalry_` prefix and mostly follow a verb_noun pattern such as `get_scene_info`, `create_layer`, and `set_attributes`. Minor deviations like `playback_control` and `add_to_render_queue` break the strict pattern but do not harm readability.

    Tool Count3/5

    Eighteen tools is on the heavier side and the count falls in the 16-25 borderline range. The breadth is understandable for a motion-graphics automation bridge, but a few tools could be consolidated, such as merging `get_comp_layers` and `get_selected_layers` or `render_queue` and `add_to_render_queue`.

    Completeness4/5

    The toolset covers the main workflows: scene inspection, layer creation, attribute manipulation, graph connections, animation keyframing, timeline control, and rendering. Obvious gaps like composition management or render queue status checking are missing, but the core lifecycle is well represented for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources