Help
Troubleshooting
Common problems, their causes, and step-by-step fixes.
MCP not connected
Claude says the After Effects tools are unavailable or "MCP not connected".
Check license key format
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX — no spaces before or after. Copy-paste directly from your dashboard.Restart your MCP client
Verify Node.js is installed
node --version in a terminal — you need v18 or newer. Install from nodejs.org if missing.Tools run but nothing happens in After Effects
Claude confirms the tool ran successfully, but no changes appear in AE.
After Effects must be open
No blocking dialogs
Active project required
After Effects not found
Error message like "Could not find After Effects" or "AfterFX.exe not found".
Set AE_AFTERFX_PATH manually
Windows example
"AE_AFTERFX_PATH": "C:\\Program Files\\Adobe\\Adobe After Effects 2025\\Support Files\\AfterFX.exe"
macOS example
"AE_AFTERFX_PATH": "/Applications/Adobe After Effects 2025/Adobe After Effects 2025.app"
License invalid or rejected
Server logs or Claude reports "invalid license key" or "license validation failed".
Copy-paste from dashboard
Check the format
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX. No quotes inside the value, no extra whitespace.Check device limit
Script timeout
Tool call returns a timeout error, especially on heavy operations like multi-layer renders.
Increase AE_MCP_TIMEOUT
AE_MCP_TIMEOUT to a higher value in milliseconds. The default is 30000 (30 seconds). For complex scripts, try 60000 or 120000.Config example
"env": {
"AE_MCP_LICENSE": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"AE_MCP_TIMEOUT": "60000"
}Expression errors after baking
After calling bake_expression, the property shows errors or incorrect values.
Check expression syntax before baking
list_expression_errors to check for errors on a property before baking. Baking a broken expression will produce incorrect baked values.Bake at correct time range
Undo is available
undo to restore the expression.Getting debug logs
Set AE_MCP_LOG_LEVEL to debug in your config to see verbose output from the MCP server. This shows exactly which scripts are sent to AE and what responses come back — useful for diagnosing unexpected behavior.
"env": {
"AE_MCP_LICENSE": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"AE_MCP_LOG_LEVEL": "debug"
}