🎨 After Effects MCP Server

Created By
WaliAhmed91a year ago
MCP Server for Adobe After Effects. Enables remote control (compositions, text, shapes, solids, properties) via the Model Context Protocol using ExtendScript.
Overview

What is After Effects MCP Server?

The After Effects MCP Server is a tool that enables remote control of Adobe After Effects using the Model Context Protocol (MCP) via ExtendScript, allowing users to manipulate compositions, text, shapes, solids, and properties seamlessly.

How to use After Effects MCP Server?

To use the MCP Server, clone the repository, install the dependencies, start the server, and connect to After Effects using ExtendScript to control various properties of your project.

Key features of After Effects MCP Server?

  • Remote control of Adobe After Effects.
  • Utilizes Model Context Protocol for effective communication.
  • Integrates with ExtendScript for scripting capabilities.
  • Automates tasks to save time and improve efficiency.
  • Supports manipulation of multiple properties including compositions, text, shapes, and solids.
  • Cross-platform compatibility with Windows and macOS.

Use cases of After Effects MCP Server?

  1. Automating repetitive tasks in After Effects.
  2. Remote collaboration on motion graphics projects.
  3. Streamlining workflows for video editing and animation.

FAQ from After Effects MCP Server?

  • Can I control all aspects of After Effects?

Yes, you can control various aspects including compositions, text, shapes, and properties.

  • Is it compatible with both Windows and macOS?

Yes, the MCP Server is designed to work on both platforms.

  • How do I start the server?

You can start the server by running the command node server.js after installing the necessary dependencies.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
WaliAhmed91
Star
6
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago