A
licenseB
qualityB
maintenanceA production-minded Model Context Protocol server for Adobe After Effects that enables AI agents to control motion graphics, editorial planning, and rendering.
48
7 npm
4
MIT
mcp-after-effects
by Dakkshin
Related Servers
Alternatives to mcp-after-effects
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceMCP server for controlling Adobe After Effects, enabling AI assistants to create compositions, manage layers, and animate properties.1349 npmMIT
- AlicenseCqualityCmaintenanceAn MCP server that enables AI assistants to control Adobe After Effects with 70+ tools for compositing, animation, effects, and motion graphics.687 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that allows AI agents to control Adobe After Effects, enabling project inspection, composition creation, layer addition, file import, ExtendScript execution, and rendering via aerender.11MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to control Adobe After Effects through a file-based communication bridge. It supports various operations including project and composition management, layer and keyframe manipulation, rendering, and batch processing.9229 npm21MIT
- AlicenseBqualityBmaintenanceMCP server that lets AI assistants control Adobe After Effects via natural language, enabling composition and layer creation, animation, effects, presets, rendering, and arbitrary ExtendScript execution with Arabic/RTL support.5049 npmMIT
TDQS
C2.9/5.0
Scored across 13 tools
Disambiguation2/5
There is significant overlap and confusion between tools: 'apply-effect' and 'mcp_aftereffects_applyEffect' appear to be duplicates with identical descriptions, as do 'apply-effect-template' and 'mcp_aftereffects_applyEffectTemplate'. Additionally, 'get-help', 'mcp_aftereffects_get_effects_help', and 'run-bridge-test' all seem related to help/testing but with unclear distinctions, making it hard for an agent to choose correctly.
Naming Consistency2/5
The naming is highly inconsistent: there's a mix of snake_case ('apply-effect'), camelCase ('setLayerExpression'), and prefixed snake_case ('mcp_aftereffects_applyEffect'). Some tools use verbs like 'run' or 'test', while others are more descriptive like 'get-results', leading to a chaotic pattern that lacks predictability.
Tool Count4/5
With 13 tools, the count is reasonable for an After Effects integration, covering various operations like composition creation, effect application, scripting, and animation testing. It's slightly on the higher side but still manageable and appropriate for the domain's complexity.
Completeness3/5
The tool set covers key areas such as composition creation, effect application, scripting, and animation, but there are notable gaps: for example, there's no tool for deleting or updating compositions/effects, and lifecycle management (e.g., save, export projects) is missing. This could lead to agent workarounds for basic operations.
Maintenance
ActivityInactive
ResponsivenessUnresponsive