mcp-after-effects
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run-scriptA | Run a read-only script in After Effects |
| get-resultsA | Get results from the last script executed in After Effects |
| get-helpB | Get help on using the After Effects MCP integration |
| create-compositionA | Create a new composition in After Effects with specified parameters |
| setLayerKeyframeB | Set a keyframe for a specific layer property at a given time. |
| setLayerExpressionB | Set or remove an expression for a specific layer property. |
| test-animationD | Test animation functionality in After Effects |
| apply-effectC | Apply an effect to a layer in After Effects |
| apply-effect-templateB | Apply a predefined effect template to a layer in After Effects |
| mcp_aftereffects_applyEffectC | Apply an effect to a layer in After Effects |
| mcp_aftereffects_applyEffectTemplateC | Apply a predefined effect template to a layer in After Effects |
| mcp_aftereffects_get_effects_helpB | Get help on using After Effects effects |
| run-bridge-testA | Run the bridge test effects script to verify communication and apply test effects |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list-compositions | List compositions in the current After Effects project |
| analyze-composition | |
| create-composition | Create a new composition with specified settings |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| compositions |
TDQS
Scored across 13 tools
There is significant overlap and confusion between tools: 'apply-effect' and 'mcp_aftereffects_applyEffect' appear to be duplicates with identical descriptions, as do 'apply-effect-template' and 'mcp_aftereffects_applyEffectTemplate'. Additionally, 'get-help', 'mcp_aftereffects_get_effects_help', and 'run-bridge-test' all seem related to help/testing but with unclear distinctions, making it hard for an agent to choose correctly.
The naming is highly inconsistent: there's a mix of snake_case ('apply-effect'), camelCase ('setLayerExpression'), and prefixed snake_case ('mcp_aftereffects_applyEffect'). Some tools use verbs like 'run' or 'test', while others are more descriptive like 'get-results', leading to a chaotic pattern that lacks predictability.
With 13 tools, the count is reasonable for an After Effects integration, covering various operations like composition creation, effect application, scripting, and animation testing. It's slightly on the higher side but still manageable and appropriate for the domain's complexity.
The tool set covers key areas such as composition creation, effect application, scripting, and animation, but there are notable gaps: for example, there's no tool for deleting or updating compositions/effects, and lifecycle management (e.g., save, export projects) is missing. This could lead to agent workarounds for basic operations.