MCP aftereffects: MCP server, setup and security

What MCP aftereffects does

According to its repository: “MCP server for Adobe After Effects — comp/layer introspection, undo-grouped ops, frame rendering.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. MCP aftereffects is listed under Other integrations, a category of 194 servers in the directory, where it ranks #66 by stars.

Installing and connecting MCP aftereffects

Distribution modes declared in the official MCP registry:

• npm package (Node.js, usually started with npx)

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to MCP aftereffects. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on August 8, 2026, the kumoproductions/mcp-aftereffects repository has 132 stars and 9 forks, with 1 open issues. It has more stars than 71% of the servers in the directory. It received changes this month. Version published in the registry: 0.3.1 (September 29, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.