home / mcp / π¬ after effects mcp server
MCP Server for Adobe After Effects. Enables remote control (compositions, text, shapes, solids, properties) via the Model Context Protocol using ExtendScript.
Configuration
View docs{
"mcpServers": {
"dakkshin-after-effects-mcp": {
"command": "node",
"args": [
"C:\\\\Users\\\\Dakkshin\\\\after-effects-mcp\\\\build\\\\index.js"
]
}
}
}You can run a local MCP server that lets AI assistants and other apps control Adobe After Effects through a standardized protocol. This server exposes functions to create compositions, manage layers, and animate properties, making it practical to automate AE workflows from external tools.
To use the server with an MCP client, start both the server process and the After Effects bridge panel. The client sends commands to create compositions, add layers, and set keyframes or expressions. You will typically follow a pattern of starting the server, loading the bridge panel in After Effects, and then issuing commands from your AI or automation tool as you work on a project. Ensure the bridge panel is configured to auto-run commands so new requests execute without manual input.
Prerequisites: you need Adobe After Effects (2022 or later) and Node.js (v14 or later). You also should have npm or yarn installed on your system.
Step 1: Clone the MCP server repository locally and navigate into it.
Step 2: Install dependencies.
npm install
# or
yarn installStep 3: Build the project.
npm run build
# or
yarn buildStep 4: Install the After Effects panel so the bridge can interact with AE.
npm run install-bridge
# or
yarn install-bridgeStep 5: Configure the MCP client to recognize this server. Use the provided example to point your client at the local runtime that will start the server.
{
"mcpServers": {
"AfterEffectsMCP": {
"command": "node",
"args": ["C:\\Users\\Dakkshin\\after-effects-mcp\\build\\index.js"]
}
}
}Step 6: Run the server. Start the MCP server process so it can listen for commands from your MCP client.
npm start
# or
yarn startStep 7: In After Effects, open the MCP Bridge Auto panel to connect to the running server. In AE, go to Window > mcp-bridge-auto.jsx. Ensure the panel is set to Auto-run commands so new requests are executed automatically.
If you need to adjust how the client talks to the server, place or modify the MCP configuration accordingly. The initial local configuration uses a stdio approach where the server runs as a local node process and AE communicates through the bridge panel.
Once the server is running and the bridge panel is open, you can start issuing commands such as creating compositions, adding text or shape layers, and applying keyframes or expressions. Use your MCP clientβs tooling to send these commands to the server, and the panel will execute them in After Effects.
- Ensure Node.js and the correct AE version are installed before starting. - Verify the bridge panel is visible in After Effects and that Auto-run is enabled. - If commands donβt execute, check that the server process started successfully and that the path to the built index.js file is correct. - Make sure the MCP client config points to the running command and its arguments exactly as shown in the example.
Limit access to the machine running the MCP server and the After Effects bridge to trusted environments. Only expose the MCP endpoint to applications you control and review any environment variables or keys used by your client.
Create a new composition with customizable settings such as name, width, height, frame rate, duration, and background color.
Run a JavaScript script inside After Effects to perform complex or repetitive tasks.
Retrieve results from a previously run script or operation to inspect outcomes.
Provide help for available MCP commands and how to use them.
Add or modify a keyframe on a layer property (e.g., position, scale, rotation, opacity).
Attach or modify expressions on layer properties for dynamic, procedural animations.