Skip to main content
Glama
Dsrupt-Technologies

Dsrupt After Effects MCP

by Dsrupt-Technologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Dsrupt After Effects MCP

No user-submitted related servers found.

    Related Servers

    • AfterEffects-MCP-IMT

      Immersive-Media-Technologies
      A
      license
      A
      quality
      A
      maintenance
      Lets AI agents drive a running Adobe After Effects — projects, comps, layers, effects, keyframes, text, masks, expressions and frames — through a small tool surface with dry-run validation and undo-grouped operations. Works with every UI language After Effects ships, comes with a large skills library and is built for AI and generative features: Roto Brush, Object Matte, Content-Aware Fill.
      4
      12
      39 npm
      2
      Apache 2.0

    • AE Bridge MCP

      NeuralIO444
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to inspect and control a live Adobe After Effects session, including reading active composition and layer data and evaluating arbitrary ExtendScript.
      4
      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
      13 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

    A4.1/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools are clearly scoped by AE object level (project/comp/layer) or function (render, save, import/export). ae_context and ae_project_info overlap somewhat in ambient/project state, and ae_version_info/ae_context both ask to be called at session start, but descriptions distinguish them sufficiently.

    Naming Consistency4/5

    The ae_ prefix and snake_case are consistent, with an info suffix for read-only inspectors and verb_noun names for actions. The generic ae_do and noun-only ae_context/ae_catalog deviate slightly from a strict verb_noun pattern, but the convention is still predictable.

    Tool Count5/5

    12 tools is well within the ideal range and each tool serves a meaningful role in the AE workflow. The count feels appropriately scoped without redundancy or bloat.

    Completeness4/5

    The set covers inspection at project/comp/layer levels, mutation through ae_do, visual verification via ae_render_frame, persistence, and full JSON round-tripping. Minor gaps like an explicit undo/redo tool or direct project lifecycle operations exist, but they are largely addressable through ae_do/operations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources