After Effects MCP Server
Related Servers
Alternatives to After Effects MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI assistants to control Adobe After Effects for composition, layer, effect, preset, marker, and audio automation through a bridge panel.3085 npm18MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to control Adobe After Effects through the MCP protocol, including composition creation, layer management, and animation.1385 npmMIT
- AlicenseCqualityCmaintenanceEnables AI assistants and applications to control Adobe After Effects through the Model Context Protocol for composition, layer management, and animation.1385 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to control Adobe After Effects for project inspection, composition creation, and layer manipulation via a hardened bridge panel.-
- AlicenseCqualityCmaintenanceEnables AI assistants and applications to control Adobe After Effects through the Model Context Protocol, including creating compositions, managing layers, and animating properties via keyframes and expressions.1385 npmMIT
- -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 10 tools
Each tool has a distinct purpose: keyframe tools are differentiated by single/multiple and layer/effect scope, and the rest target different operations (composition, import, render, export, help, script execution). No two tools are easily confused.
Most tools follow a camelCase verbNoun pattern (createComposition, setLayerKeyframes, importFootage). The only exception is run-script, which uses lowercase with a hyphen, creating a minor inconsistency.
With 10 tools, the set is well-scoped for After Effects automation—covering composition creation, footage import, animation, rendering, and frame export. Each tool earns its place without redundancy.
The toolset covers core workflows but misses common operations like adding layers, setting static layer properties, or managing project files. The run-script tool can mitigate these gaps, but it is a workaround rather than a dedicated interface.