Agent-driven Adobe After Effects automation. MCP server + CEP plugin enabling Codex/Cursor/Claude Code to drive AE th...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 57/100. no security policy. 24 open issues make this testable, but not something to trust blind.
AI Agent
Multiple
Model
Claude
Fastest way to find out if after-effects-mcp belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add after-effects-mcp -- npx after-effects-mcpRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove after-effects-mcpNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ after-effects-mcp ← registers here
Agent-driven Adobe After Effects automation. MCP server + CEP plugin enabling Codex/Cursor/Claude Code to drive AE through 30 ae.* tools.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 18, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.