After Effects MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AFTERAI_API_KEY | Yes | Your afterAI key from /api-access. | |
| AFTERAI_BASE_URL | No | Override the API base URL. | https://getafterai.eu |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| edit_videoA | Submit a raw clip to afterAI's After Effects cloud pipeline. Returns a job id and a tracking URL. Spends one credit from your plan. The finished video is emailed to the account that owns the API key. Use check_status to follow progress. videoUrl must be a public, direct link to the raw clip. |
| check_statusA | Look up the live status of a submitted edit by its job id (the id returned by edit_video). Returns progress percent, the current stage and, when done, the download link. |
| afterai_infoA | Explains what afterAI does, the available edit options and how to get an API key and plan. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: edit_video submits a job, check_status tracks it, and afterai_info provides general information. No overlap or ambiguity.
edit_video and check_status follow the verb_noun pattern, but afterai_info breaks the convention as a noun phrase rather than a verb-based command, creating a minor inconsistency.
Three tools is well-scoped for a simple cloud rendering workflow: submit, poll status, and get info. Each tool serves a necessary role without unnecessary bloat.
The tool surface covers the full lifecycle from submission to result retrieval via the download link in check_status. No critical operations are missing for the advertised purpose.