mcp-aftereffects
Related Servers
Alternatives to mcp-aftereffects
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityBmaintenanceA local MCP server that connects AI agents to Adobe After Effects, enabling reliable project inspection, reasoning, and controlled mutations through structured tools and typed patches.43,837 npmMIT
- AlicenseCqualityCmaintenanceLocal MCP server to control Adobe After Effects from AI clients like Claude and Cursor, supporting project composition, layer editing, animation, masks, and effects.13104 npmMIT
- 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.50104 npmMIT
- AlicenseCqualityCmaintenanceMCP server for controlling Adobe After Effects, enabling AI assistants to create compositions, manage layers, and animate properties.13104 npmMIT
- AlicenseBqualityBmaintenanceA production-minded Model Context Protocol server for Adobe After Effects that enables AI agents to control motion graphics, editorial planning, and rendering.4813 npm4MIT
TDQS
Scored across 11 tools
Each tool has a clearly distinct target: project info, comp info, layer info, render, save, serialization, version, catalog, execution, and context. Even overlapping concepts like project_info and context are separated by their descriptions—one returns project details, the other ambient session state and undo rules.
All tools share the ae_ prefix and use lowercase snake_case consistently. Names follow a readable verb_noun or resource_info pattern (render_frame, save_project, project_export_json, layer_info), with only ae_do and ae_catalog as short verbs/nouns, but they still fit the same naming style.
Eleven tools is well within the ideal range for an After Effects automation server. The set is well-scoped: read operations, a render check, project save/export/import, and a generic operation mechanism with discovery. Each tool earns its place without redundancy.
The surface covers project lifecycle, inspection, rendering, JSON serialization/deserialization, and an extensible atomic operation path via ae_catalog/ae_do. Minor gap: common mutations are not individually exposed as top-level tools, but the catalog/do pair makes them discoverable and executable, so workflows are not blocked.