AE Motion MCP
Related Servers
Alternatives to AE Motion MCP
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityCmaintenanceEnables Claude to inspect and build compositions in an open Adobe After Effects project, animate layers and effects, preview real frames, compare against reference video side by side, measure and recreate camera moves, detect cuts and beats, and render MP4s.MIT
- AlicenseCqualityBmaintenanceEnables Claude to drive Adobe After Effects: creating comps and layers, setting real keyframes with temporal and spatial easing, inspecting and sampling animation curves, and rendering PNG stills or MP4 output so the AI can review its own work.25MIT
- AlicenseNot gradedqualityCmaintenanceLets Claude Code or any MCP client drive an open Adobe After Effects instance to inspect projects and comps, build and animate layers with ExtendScript, preview frames as images, import footage, and render comps with live progress reporting. All changes land as single undoable steps, and communication stays local through a token-protected bridge.182 npmMIT
- AlicenseAqualityBmaintenanceConnects Claude to a running Adobe After Effects so it can build eased keyframes, motion presets, kinetic typography, PSD-to-animation scenes, transitions and speed ramps, then review, polish and render deliverables. It also exposes a knowledge base of motion-design notes plus 262 operations across the full After Effects surface, with each edit applied as a single undo step.1812MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to control Adobe After Effects through a standardized MCP protocol, providing tools for composition creation, layer management, and animation.-
TDQS
Scored across 46 tools
Most tools target a clearly distinct resource+action (set_property vs set_keyframes vs edit_keyframes vs copy_animation are explicitly delimited, and get_text/get_layer/list_properties are separated by granularity). A few pairs need reading the description to separate (get_comp vs get_project vs get_layer, apply_effect vs edit_effect vs apply_preset), but the descriptions disambiguate them and set_property even points to set_text for text.
Consistent snake_case with a mostly verb_noun shape (get_layer, set_keyframes, delete_item, render_start, find_fonts). A handful are bare verbs or verb-object without a resource noun (precompose, stagger, animate, transition, batch), which is readable but a minor deviation from the dominant pattern.
46 exposed tools is well above the comfortable range for a single server surface, even for a large domain like After Effects automation. The load_tools progressive-disclosure groups mitigate this somewhat by deferring timeline, masks, scene3d, audio and scripting tools, but the top-level set is still heavy and increases selection cost.
Core lifecycle is covered end to end: projects (open/save/import), comps, layers, properties, keyframes, expressions, effects, text, previews and renders with polling/cancel. Gaps are minor and mostly deferred rather than missing (splitting, masks, cameras/lights, markers, audio live in load_tools groups), and there is no top-level undo control.