Skip to main content

dcc-mcp-aftereffects

DCC-MCP · AFTEREFFECTS

Part of the DCC-MCP host matrix

dcc-mcp-aftereffects — Adobe After Effects adapter with typed project, layer, render queue, and official DOM workflows.

It is one of 47 host adapters in the DCC-MCP catalog. Every adapter speaks the same MCP protocol and builds on the same core runtime contract; each one exposes the tools its own host needs on top of that.

This block is generated from the catalog entry in dcc-mcp-catalog.yml. Re-run the generator after changing the catalog.

Agent workflow

AI agents should use the shared gateway through dcc-mcp-cli; IDE users may continue to use the MCP endpoint. Prefer typed skills and tools over raw scripts.

Install or update the CLI

dcc-mcp-cli is the preferred control path for every shell-capable agent. If it is missing, ask the user before installing the latest official release:

# Linux/macOS
curl -fsSL https://raw.githubusercontent.com/dcc-mcp/dcc-mcp-core/main/scripts/install-cli.sh | sh

# Windows PowerShell
powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/dcc-mcp/dcc-mcp-core/main/scripts/install-cli.ps1 | iex"

Keep an official build current through the release manifest:

dcc-mcp-cli update check
dcc-mcp-cli update apply

update apply downloads and stages the latest CLI for the next launch. It does not update a running dcc-mcp-server; update that server in its own environment.

dcc-mcp-cli dcc-types
dcc-mcp-cli list
dcc-mcp-cli search --query "<task>" --dcc-type aftereffects
dcc-mcp-cli describe <tool-slug>
dcc-mcp-cli call <tool-slug> --json '{"key":"value"}'

dcc-types reports release-catalog support; list reports live sessions. If a tool belongs to an inactive progressive skill, call dcc-mcp-cli load-skill <skill-name> --dcc-type aftereffects before retrying. For post-task improvement, attach a stable session id with --meta-json, query dcc-mcp-cli stats --range 24h --session-id <task-id>, then pass the bounded evidence to the review_skill_improvement prompt from dcc-mcp-skills-creator.

MCP adapter for Adobe After Effects, built on the shared adobepy broker, CEP bridge, and typed facade.

pip install dcc-mcp-aftereffects

Use the standard adapter-owned lifecycle; it stages the official adobepy CEP bridge without putting ADOBEPY_TOKEN in process arguments:

dcc-mcp-aftereffects install --json --dry-run --dcc-path "<host>" --python "<python>"
dcc-mcp-aftereffects install --json --yes --dcc-path "<host>" --python "<python>"
dcc-mcp-aftereffects verify --json --dcc-path "<host>" --python "<python>"

For an Internal deployment with an approved prebuilt CEP bridge, the shared CLI can link the bridge directly into the Adobe CEP extension root:

dcc-mcp-cli install --dcc-type aftereffects `
  --plugin-source F:\studio\artifacts\aftereffects-cep-bridge `
  --adobe-debug-root "$env:APPDATA\Adobe\CEP\extensions" `
  --execute

The source directory must contain the bridge manifest and is selected by an approved catalog or Internal descriptor. This path does not copy files or require a Developer Tool, but it is only valid for a bridge that has already been built and approved. The adapter-owned installer remains canonical for adobepy provisioning, generated CEP bridges, receipts, upgrades, and uninstall. Restart After Effects if it has already cached the extension, then use dcc-mcp-cli wait-ready --dcc-type aftereffects to verify the live bridge.

See install.md for supported Windows/macOS paths, the Linux boundary, adobepy CLI provisioning, receipt-driven upgrade/uninstall, stable exit codes, and troubleshooting. Each adapter instance uses an OS-assigned port and registers it for CLI discovery. Connect through the stable gateway at http://127.0.0.1:9765/mcp; set DCC_MCP_AFTEREFFECTS_PORT only when a fixed direct endpoint is required.

Set ADOBEPY_TOKEN to the same non-default token used when installing the bridge.

The adapter reports ready only after the target After Effects bridge advertises the complete typed/official-DOM contract, a real host version RPC succeeds, and trusted runtime identity is available. adobepy 0.12.0 still rejects After Effects identity until CEP launch-receipt/bootstrap support exists, so readiness remains fail-closed. The dependency update does not claim live-host support. A broker process is stopped only when it was started by this adapter.

Skill groups

  • aftereffects-project: inspect/open/save projects, list and import project items, create compositions, and run the motion-intro workflow.
  • aftereffects-layers: inspect compositions, layers, effects, masks, and text; create text/solid/footage layers; edit text, transforms, keyframes, and order.
  • aftereffects-render: inspect and control the render queue, queue compositions, and configure render settings and output modules.
  • aftereffects-advanced: structured access to the complete official object model. Raw ExtendScript is an explicit destructive fallback, not the primary API.

Load a group before first use when progressive loading is enabled:

dcc-mcp-cli load-skill aftereffects-layers --dcc-type aftereffects
dcc-mcp-cli search --query "create text layer" --dcc-type aftereffects

Metadata

Release files for dcc-mcp-aftereffects 0.7.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dcc-mcp-aftereffects 0.7.3
File Size Uploaded Provenance
dcc_mcp_aftereffects-0.7.3.tar.gz 1.1 MB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for dcc-mcp-aftereffects 0.7.3
File Interpreter ABI Platform
dcc_mcp_aftereffects-0.7.3-py3-none-any.whl Python 3 none any Details

Total release size: 1.2 MB

Release files / dcc_mcp_aftereffects-0.7.3.tar.gz

Download URL dcc_mcp_aftereffects-0.7.3.tar.gz
Size 1.1 MB
Tags Source
SHA-256 checksum
How to use checksums
490ee9078309a21230adab6ea194db46cfecc46cfc602d077933ac92d60cc0c8
BLAKE2b-256 checksum
How to use checksums
2cbb5c7c86e1365f939f286878cc94655be37c65654e0741e2b4dba2be4af73f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.

Transparency log

Release files / dcc_mcp_aftereffects-0.7.3-py3-none-any.whl

Download URL dcc_mcp_aftereffects-0.7.3-py3-none-any.whl
Size 86.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e2ca0e74ad03c6314a2788793cac38669a67fdd8457ec3b5e2a02e4f4dd41417
BLAKE2b-256 checksum
How to use checksums
f0eb39410aedfd363aa8f9877d35da52c472e29b4f2b4a4b5df98c77b4bdaa58
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.

Transparency log

Security for dcc-mcp-aftereffects 0.7.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for dcc_mcp_aftereffects-0.7.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page