aftereffects
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run-scriptA | Run one of the bridge's built-in After Effects commands and return its result. Only these commands exist; it cannot run arbitrary code. Read: listCompositions, getProjectInfo, getLayerInfo (layers of the ACTIVE composition). Compositions: createComposition {name, width, height, frameRate, duration, pixelAspect, backgroundColor:{r,g,b 0-255}}; setCompositionProperties {compName, duration, frameRate, width, height}. Layers (compName = target composition; colours are [r,g,b] from 0 to 1; position is [x,y] in pixels; times in seconds):
|
| get-resultsA | Read the last result After Effects wrote. Only needed if a command timed out because it was slow (e.g. heavy effects). |
| create-compositionC | Create a new composition in After Effects. |
| setLayerKeyframeA | Set a keyframe on a layer property at a given time. Add two or more keyframes on the same property to animate it. |
| setLayerExpressionB | Set or remove an After Effects expression on a layer property (e.g. wiggle(2,20) for gentle handheld motion). |
| apply-effectB | Apply an effect to a layer. Use get-effects-help for reliable effect match names. |
| apply-effect-templateC | Apply a predefined combination of effects to a layer. |
| view-compA | SEE a composition: renders evenly spaced frames from After Effects and returns them as one IMAGE with the time of each frame. Use it after building or animating something to check text placement, timing and motion before telling the user it is done. Defaults to the active composition. |
| run-bridge-testA | Check the connection: runs the bridge's test command in After Effects, which applies test effects to the active composition. |
| get-helpC | How to set up and use Ibintec After Effects MCP. |
| get-effects-helpC | Effect match names and the predefined effect templates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list-compositions | List compositions in the current After Effects project |
| analyze-composition |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| compositions |
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes (run-script runs built-in commands, create-composition creates a comp, setLayerKeyframe animates, view-comp renders). However, the first tool 'run-script' is a meta-tool that overlaps with many named commands, and 'create-composition' appears to duplicate the createComposition command listed inside run-script, creating some confusion. 'apply-effect' vs 'apply-effect-template' and 'setLayerProperties' vs 'batchSetLayerProperties' are distinguishable but require reading descriptions.
Mixed conventions: snake_case for top-level tools (run-script, setLayerKeyframe, apply-effect), while the description lists camelCase built-in commands (getProjectInfo, createTextLayer, setLayerProperties). The hyphen/underscore and camelCase inconsistency across the surface makes the set feel like two conventions bolted together.
11 top-level tools is well-scoped for an After Effects automation bridge, though the tool docs disclose a much larger hidden repertoire of built-in commands funneled through run-script, which somewhat undercuts the count's meaning.
Core lifecycle is decently covered (create comp, layers, keyframes, expressions, effects, view), but deleting compositions, listing effects on layers, and exporting/rendering are absent. The heavy reliance on run-script's unlisted built-ins suggests the explicit surface has notable gaps.