A
licenseA
qualityB
maintenanceEnables local control of Adobe After Effects via MCP, offering offline creative skills, project inspection, and operation execution without cloud relay or an installed AE panel.
12
2,219 npm
13
MIT
after-effects-mcp-enhanced
by ku1x
Related Servers
Alternatives to after-effects-mcp-enhanced
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables controlling Adobe After Effects from an MCP client through a bridge panel running inside AE. Supports composition and layer automation, effect and preset application, keyframing, markers, and audio waveform analysis for generating markers.3062 npmMIT
- AlicenseCqualityDmaintenanceLocal MCP server to control Adobe After Effects from AI clients like Claude and Cursor, supporting project composition, layer editing, animation, masks, and effects.1362 npmMIT
- 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.62 npmMIT
- AlicenseCqualityDmaintenanceEnables AI assistants to control Adobe After Effects through the MCP protocol, including composition creation, layer management, and animation.1362 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Adobe After Effects, enabling structured control over projects, compositions, layers, properties, expressions, keyframes, imports, and rendering through a local authenticated WebSocket bridge.62 npmMIT
TDQS
A3.7/5.0
Scored across 11 tools
Disambiguation4/5
Each tool targets a distinct operation such as bridge management, import, save, render, or script execution. The pairs get-request/get-render and run-command/execute-jsx are similar, but their descriptions clearly separate general request status from aerender jobs and predefined commands from arbitrary ExtendScript.
Naming Consistency4/5
Most tools follow a clear verb-noun hyphenated pattern like list-installations, launch-bridge, save-project, and render-composition. bridge-status is the one notable deviation since it leads with a noun rather than a verb, but the overall naming is predictable and consistent.
Tool Count5/5
11 tools is well within the ideal range and each tool earns its place in the After Effects automation workflow. The count covers bridge setup, asset import, project saving, rendering, and script execution without unnecessary redundancy.
Completeness4/5
The tool surface covers the main lifecycle needs: discovering and launching AE, importing footage, saving projects, rendering, and running scripts or commands. Missing operations like opening or creating projects and listing compositions are workable through execute-jsx, so the gaps are minor rather than blocking.
Maintenance
ActivitySlowing
ResponsivenessNo issues