A Model Context Protocol server for Adobe After Effects automation and tool library management
After Effects MCP has 13 tools with complete input schemas and descriptions, but quality is uneven. Tool names follow verb_noun convention (ae_exec, ae_read, ae_checkpoint) which is good. However, descriptions are often generic or lack actionable context for LLM selection. Parameters are typed but many lack detailed constraints or format guidance. Output schemas are not documented in the provided source. Error handling is minimal, no recovery guidance or categorization. The tool library integration (ae_toolSearch, ae_toolUse, ae_toolSave) is sophisticated but underdocumented. STDIO transport caps protocol readiness at 50.
Create a checkpoint of the current After Effects project state
Execute JSX code in After Effects with approval gating and result parsing
Recover from execution errors with diagnostic information
Execute native After Effects operations with direct API access
Capture and return a preview frame from the current After Effects composition
Read data from After Effects project without modification
Revert After Effects project to a previous checkpoint
Execute a skill from the skill library with optional arguments
Output schemas not documented. Tools like ae_exec, ae_read, ae_previewFrame return results but no schema is visible in source. LLMs cannot plan downstream calls or extract fields without knowing response structure.
Generic parameter descriptions. ae_read accepts 'query' with description 'Query to read from the project', does not explain format, syntax, or valid query types. ae_nativeExec 'operation' and 'args' are similarly vague.
No error handling guidance. Tools declare risk levels (WRITE, REVERSIBLE) but provide no recovery hints. If ae_exec fails, LLM has no guidance on whether to retry, call ae_execRecover, or ask user.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2025-06-18+ | v2 |
Get current After Effects project status and state
Turn a useful script into a reusable tool, or promote a captured candidate in one step.
Search the Tool Library before repeating an operation; saved tools and candidates can both be inspected directly by id.
Replay a Tool Library artifact by id. Prefer it over rewriting a script for a repeated task.
Validate After Effects expressions for syntax and runtime errors
Tool library tools (ae_toolSearch, ae_toolUse, ae_toolSave) lack clear composition guidance. Descriptions do not explain when to use ae_toolSearch vs ae_toolUse, or how artifact IDs flow between them.
ae_exec timeout parameter lacks constraints. No minimum/maximum specified; LLM could pass 0, negative, or absurdly large values. Should specify range (e.g. 100 - 300000 ms).