Skip to main content
Glama

Related Servers

Alternatives to ae-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.5/5.0

    Scored across 17 tools

    Disambiguation3/5

    Most tools map to distinct After Effects domains (project, comp, layer, property, keyframes, text, shape, mask, effect, rig, render), so an agent can usually tell them apart. However, ae_run explicitly covers everything the other tools do, and ae_property overlaps with ae_effect, ae_shape, and ae_mask for property-level manipulation. The descriptions help by positioning ae_run as low-level kernel access and ae_eval/ae_ui as fallbacks, but the boundaries are not always crystal clear.

    Naming Consistency4/5

    All tool names share a consistent ae_ prefix and lowercase snake_case style, which gives the set a strong visual and structural identity. The pattern is not uniformly verb_noun—most names are resource nouns like ae_comp or ae_layer, while a few are action verbs like ae_run or ae_render—but this deviation is minor and the naming remains readable and predictable.

    Tool Count4/5

    At 17 tools, the server sits slightly above the ideal 3-15 range, but After Effects automation genuinely requires coverage across project, composition, layer, properties, keyframes, effects, rendering, and UI control. Each tool covers a substantial functional area, so the count feels justified rather than padded.

    Completeness5/5

    The tool surface is remarkably complete: it covers project/comp/layer lifecycle, property and expression editing, keyframes and animation presets, text/shape/mask/effect manipulation, rigging, rendering, and even arbitrary menu/script fallbacks. ae_run, ae_ui, and ae_eval seal any remaining gaps, leaving no obvious dead ends for AE automation workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing