MCP server for controlling Adobe After Effects through a local Node bridge and ScriptUI panel for compositions, layers, keyframes, expressions, masks, and effects.
After Effects MCP queues predefined commands to a local bridge directory and relies on an open After Effects ScriptUI panel to execute them., The bridge can create compositions, text layers, shape layers, solid layers, cameras, null objects, masks, keyframes, expressions, effects, and layer property changes., Layer duplication, layer deletion, expression changes, masks, timing edits, and batch property updates can materially alter an After Effects project., The install script may copy files into Adobe application folders and may require elevated privileges on some systems., Enabling After Effects scripting permissions can let scripts write files and access network resources, so keep the bridge limited to trusted projects., Use only the predefined script list exposed by the MCP server; do not modify it to accept arbitrary scripts unless that risk is understood.
Privacy notes
Tool calls and results can expose composition names, project structure, layer names, layer properties, timing, expressions, effect names, masks, and local bridge file paths., Project contents may include client work, unreleased media, brand assets, filenames, text layers, and animation details., The command and result files in the local bridge directory can persist recent instructions and After Effects output., MCP client logs and model context may retain prompts, layer names, generated expressions, and project metadata.
Author
Dakkshin
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
6 safety and 4 privacy notes across 5 risk areas. Review closely: permissions & scopes.
5 areas
SafetyLocal filesAfter Effects MCP queues predefined commands to a local bridge directory and relies on an open After Effects ScriptUI panel to execute them.
SafetyGeneralThe bridge can create compositions, text layers, shape layers, solid layers, cameras, null objects, masks, keyframes, expressions, effects, and layer property changes.
SafetyGeneralLayer duplication, layer deletion, expression changes, masks, timing edits, and batch property updates can materially alter an After Effects project.
SafetyPermissions & scopesThe install script may copy files into Adobe application folders and may require elevated privileges on some systems.
SafetyPermissions & scopesEnabling After Effects scripting permissions can let scripts write files and access network resources, so keep the bridge limited to trusted projects.
SafetyExecution & processesUse only the predefined script list exposed by the MCP server; do not modify it to accept arbitrary scripts unless that risk is understood.
PrivacyLocal filesTool calls and results can expose composition names, project structure, layer names, layer properties, timing, expressions, effect names, masks, and local bridge file paths.
PrivacyLocal filesProject contents may include client work, unreleased media, brand assets, filenames, text layers, and animation details.
PrivacyLocal filesThe command and result files in the local bridge directory can persist recent instructions and After Effects output.
PrivacyData retentionMCP client logs and model context may retain prompts, layer names, generated expressions, and project metadata.
Disclosure: MIT-licensed source-install MCP server for Adobe After Effects. This entry is distinct from generic design or image tools because it controls After Effects through a local Node MCP server plus an ExtendScript ScriptUI bridge panel.
Safety notes
After Effects MCP queues predefined commands to a local bridge directory and relies on an open After Effects ScriptUI panel to execute them.
The bridge can create compositions, text layers, shape layers, solid layers, cameras, null objects, masks, keyframes, expressions, effects, and layer property changes.
Layer duplication, layer deletion, expression changes, masks, timing edits, and batch property updates can materially alter an After Effects project.
The install script may copy files into Adobe application folders and may require elevated privileges on some systems.
Enabling After Effects scripting permissions can let scripts write files and access network resources, so keep the bridge limited to trusted projects.
Use only the predefined script list exposed by the MCP server; do not modify it to accept arbitrary scripts unless that risk is understood.
Privacy notes
Tool calls and results can expose composition names, project structure, layer names, layer properties, timing, expressions, effect names, masks, and local bridge file paths.
Project contents may include client work, unreleased media, brand assets, filenames, text layers, and animation details.
The command and result files in the local bridge directory can persist recent instructions and After Effects output.
MCP client logs and model context may retain prompts, layer names, generated expressions, and project metadata.
Prerequisites
Adobe After Effects 2022 or newer.
Node.js, npm, and a local checkout of the repository.
Permission to install the ScriptUI panel into the After Effects ScriptUI Panels folder.
After Effects scripting preferences reviewed, including whether scripts may write files and access the network.
A current project backup before allowing model-driven composition or layer edits.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
20 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
MIT-licensed source-install MCP server for Adobe After Effects. This entry is distinct from generic design or image tools because it controls After Effects through a local Node MCP server plus an ExtendScript ScriptUI bridge panel.
After Effects MCP Server connects Claude and other MCP clients to Adobe After
Effects through a local Node.js MCP server and an ExtendScript ScriptUI bridge
panel. The MCP server writes command files, the panel polls for those commands
inside After Effects, and results are returned through a local result file.
Use it when a motion-design or video workflow needs Claude to create
compositions, add layers, inspect project information, set keyframes, apply
expressions, or adjust layer properties with predefined commands rather than
open-ended script execution.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, license, package metadata, MCP server implementation, bridge panel
script, install script, and sample MCP config for current setup and operating
details.
Features
Create After Effects compositions with custom name, size, frame rate,
duration, and background color.
List compositions and inspect project or layer information.
Create text layers with position, font, size, color, alignment, start time,
and duration.
Create rectangle, ellipse, polygon, and star shape layers with fill, stroke,
size, position, and timing settings.
Create solid or adjustment layers.
Create camera and null layers for animation control.
Set layer position, scale, rotation, opacity, blend mode, 2D or 3D mode,
enabled state, timing, and track matte settings.
Add keyframes and expressions to layer properties.
Apply effects and effect templates.
Duplicate or delete layers.
Create or modify masks with feather, expansion, and opacity settings.
Batch apply layer properties to multiple layers.
Read bridge results through the get-results tool.
Installation
Clone and build the server:
git clone https://github.com/Dakkshin/after-effects-mcp.git
cd after-effects-mcp
npm install
npm run build
Open After Effects, enable the required scripting preference only if you trust
the bridge workflow, then open the mcp-bridge-auto.jsx panel from the Window
menu.
Use Cases
Generate a new composition layout from a design prompt.
Add text, shape, solid, camera, and null layers for a motion-graphics scene.
Adjust layer timing, opacity, position, scale, rotation, blend mode, and 3D
state.
Add expressions or keyframes for procedural animation.
Inspect composition and layer metadata before planning edits.
Apply a sequence of predefined layer changes across multiple selected or named
layers.
Prototype animation ideas while keeping commands constrained to a known script
list.
Safety and Privacy
After Effects MCP Server changes local creative project files through Adobe's
scripting system. Back up projects before experimenting, keep the bridge panel
closed when not in use, and review commands that delete layers, alter
expressions, change masks, or batch-edit many layers.
Because the bridge uses local command and result files, recent prompts,
composition names, layer metadata, and generated expressions may remain on disk
and in MCP client logs. Treat project details and media names as client or
studio data.
Duplicate Notes
Existing catalog entries cover design handoff, image generation, and other
creative tools. This entry covers the separate Dakkshin/after-effects-mcp
project for controlling Adobe After Effects through a Node MCP server and
ExtendScript bridge panel.
Show that After Effects MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/after-effects-mcp-server)
How it compares
After Effects MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
MCP server for controlling Adobe After Effects through a local Node bridge and ScriptUI panel for compositions, layers, keyframes, expressions, masks, and effects.
MCP server for controlling DaVinci Resolve Studio through the official scripting API, with tools for projects, timelines, media pools, render setup, review markers, grading, Fusion, Fairlight, and source-safe media analysis.
MCP server and CLI for AI image and video generation with gallery search, prompt enhancement, model listing, local preferences, ComfyUI workflows, MeiGen Cloud, and OpenAI-compatible provider support.
MCP and REST server for creating short-form videos from scene text, Pexels search terms, text-to-speech, captions, background music, Whisper captions, FFmpeg, and Remotion rendering.
✓After Effects MCP queues predefined commands to a local bridge directory and relies on an open After Effects ScriptUI panel to execute them.
The bridge can create compositions, text layers, shape layers, solid layers, cameras, null objects, masks, keyframes, expressions, effects, and layer property changes.
Layer duplication, layer deletion, expression changes, masks, timing edits, and batch property updates can materially alter an After Effects project.
The install script may copy files into Adobe application folders and may require elevated privileges on some systems.
Enabling After Effects scripting permissions can let scripts write files and access network resources, so keep the bridge limited to trusted projects.
Use only the predefined script list exposed by the MCP server; do not modify it to accept arbitrary scripts unless that risk is understood.
✓DaVinci Resolve MCP Server can launch or reconnect to Resolve, switch pages, create or open projects, modify timelines, manage media pools, write markers, change render settings, and queue jobs.
Extension-authoring tools can install or remove Resolve scripts, Fuses, DCTLs, ACES DCTLs, presets, and page scripts.
Source media is intended to remain immutable by default, but operators must still review requests that relink, replace, transcode, proxy, render, export, or create media derivatives.
The default server is local stdio, but the local control panel starts a single-user browser server; keep it on trusted local interfaces only.
Require confirmation before deleting projects, replacing clips, changing project settings, installing extensions, updating metadata, or queuing renders.
Keep Resolve external scripting set to `Local` unless you have a separate remote-control security plan.
✓MeiGen can submit image and video generation jobs to external providers or a local ComfyUI backend.
Image and video generation may spend credits, use paid APIs, or consume local GPU resources depending on the configured provider.
Local reference images can be compressed and uploaded through the configured upload gateway before being sent to API providers.
Video generation can take minutes, may time out at the MCP client, and should not be retried blindly because jobs or credits may already be in progress.
ComfyUI workflow import and modification can run local workflows; review workflow JSON and custom nodes before use.
✓Short Video Maker runs an HTTP server with MCP SSE routes and REST routes for creating and serving generated videos.
The create-short-video tool queues video rendering work that can consume CPU, memory, disk, browser rendering resources, and optional GPU resources.
Generated videos combine user-provided narration text, Pexels search terms, downloaded background clips, local music assets, TTS output, captions, and rendered media.
The server stores generated videos and temporary files under its configured data directory.
Validate scene text, search terms, claims, branding, and rights before publishing generated videos to TikTok, Instagram, YouTube, or other platforms.
Privacy notes
✓Tool calls and results can expose composition names, project structure, layer names, layer properties, timing, expressions, effect names, masks, and local bridge file paths.
Project contents may include client work, unreleased media, brand assets, filenames, text layers, and animation details.
The command and result files in the local bridge directory can persist recent instructions and After Effects output.
MCP client logs and model context may retain prompts, layer names, generated expressions, and project metadata.
✓Project names, timelines, clip names, media paths, markers, metadata, render paths, transcripts, thumbnails, analysis artifacts, logs, and Resolve scripting paths can be exposed to the MCP client.
Media analysis can produce sidecar files, scratch artifacts, frame paths, transcripts, searchable indexes, and reports that may include private footage details.
Host-chat visual analysis can expose selected frame images to the active MCP client or vision-capable model provider.
Local logs and analysis reports may contain absolute media paths, project names, clip metadata, speaker text, visual descriptions, and render settings.
Store generated analysis artifacts and exports inside approved project or scratch directories and delete them when no longer needed.
✓API tokens, OpenAI-compatible credentials, provider base URLs, upload gateway URLs, ComfyUI URLs, preferences, recent generations, prompts, model IDs, and output paths can reveal private creative workflows.
Uploaded reference images may become public URLs through the configured upload gateway before generation.
Prompts, reference images, generated image URLs, generated video URLs, saved outputs, and favorite prompts can contain client work, brand plans, product images, personal likenesses, or unreleased campaigns.
Keep secrets in MCP client environment configuration, review generated media before sharing, and remove local outputs when retention is no longer needed.
✓`PEXELS_API_KEY` is sent to the Pexels API when searching for background videos.
Scene text, search terms, generated narration, captions, video IDs, logs, output filenames, and render status can reveal campaign ideas, private scripts, brand plans, or client work.
Generated files remain on disk until removed according to the deployment's data-directory and retention practices.
Pexels requests, model downloads, Docker pulls, npm installs, and platform uploads may expose network metadata to third parties outside the MCP client.
Prerequisites
Adobe After Effects 2022 or newer.
Node.js, npm, and a local checkout of the repository.
Permission to install the ScriptUI panel into the After Effects ScriptUI Panels folder.
After Effects scripting preferences reviewed, including whether scripts may write files and access the network.
DaVinci Resolve Studio 18.5 or newer; the free edition does not support the required external scripting API.
Resolve external scripting set to `Local`.
Python 3.10 or newer, with Python 3.10-3.12 recommended for the broadest Resolve compatibility.
A local MCP client that can launch stdio servers under the same user account that operates Resolve.
Node.js 18 or newer.
MCP client that can launch a local Node stdio server.
Optional MeiGen API token, OpenAI-compatible API key, or local ComfyUI workflow configuration for generation tools.
Provider pricing, credits, model limits, and content policy reviewed before image or video generation.
Node.js or Docker available on the machine that will run the video server.
Pexels API key configured through `PEXELS_API_KEY`.
Enough CPU, memory, and disk for Whisper, Kokoro, FFmpeg, Remotion, temporary files, and rendered videos.
MCP client that can connect to an SSE MCP endpoint.
Install
git clone https://github.com/Dakkshin/after-effects-mcp.git && cd after-effects-mcp && npm install && npm run build
npx davinci-resolve-mcp setup
Run `npx -y meigen` from an MCP client, or use the upstream plugin/init commands after reviewing provider credentials and generated-media costs.
Run the upstream Docker image or `npx short-video-maker` with `PEXELS_API_KEY` set, then connect an MCP client to the server's `/mcp/sse` endpoint.
Config
Manual-only setup:
npm run build && npm run install-bridge