{"id":"dakkshin-after-effects-mcp","name":"after-effects-mcp","af_score":57.8,"security_score":20.2,"reliability_score":25.0,"what_it_does":"Provides an MCP (Model Context Protocol) server plus an After Effects “bridge” panel to let clients remotely control Adobe After Effects project contents—e.g., create compositions and layers, modify properties, set keyframes/expressions, and run scripts—via MCP tool calls that ultimately execute ExtendScript/JS inside After Effects.","best_when":"You have a trusted local desktop workflow where an MCP-capable client can talk to the MCP server and After Effects is available and configured.","avoid_when":"You need robust multi-tenant security, fine-grained access control, or documented rate limiting/error-code semantics; also avoid running it in a way that exposes script execution paths to untrusted users.","last_evaluated":"2026-04-04T19:32:25.534694+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"known_gotchas":["After Effects and the MCP bridge panel must be running/available; commands depend on AE state.","Tool calls that mutate the project (create/delete/duplicate, set properties) may be order-dependent.","If the bridge auto-runs periodically, agents may need to avoid sending overlapping commands.","Execution results rely on ExtendScript/After Effects timing; failures may require observing AE-side state even if MCP returns a response."],"error_quality":0.0}