A
licenseA
qualityC
maintenanceEnables local automation of Adobe After Effects 2024+ through MCP, including composition creation, arbitrary ExtendScript execution, footage import, project saving, and rendering via clients like Codex.
11
1
MIT
fnf-local-pluging-bridge-mcp
Related Servers
Alternatives to fnf-local-pluging-bridge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceLocal MCP server to control Adobe After Effects from AI clients like Claude and Cursor, supporting project composition, layer editing, animation, masks, and effects.1399 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Adobe After Effects, enabling structured control over projects, compositions, layers, properties, expressions, keyframes, imports, and rendering through a local authenticated WebSocket bridge.99 npmMIT
- AlicenseCqualityDmaintenanceEnables AI assistants to control Adobe After Effects through the MCP protocol, including composition creation, layer management, and animation.1399 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to drive Adobe After Effects via a Python server and CEP panel, supporting inspection, mutation, preview, checkpoint/revert, skills, and basic rigging.75MIT
- FlicenseBqualityDmaintenanceEnables control of Adobe After Effects via natural language, allowing project manipulation, layer creation, animation, and rendering through MCP.72-
TDQS
A4/5.0
Scored across 12 tools
Disambiguation4/5
Most tools map cleanly to a distinct concern: project info, comp info, layer info, rendering, saving, JSON serialization, and atomic execution. The only mild overlaps are ae_context vs ae_project_info, both exposing project/item state, and ae_catalog vs ae_get_skill as discovery tools, but the descriptions provide enough guidance to disambiguate.
Naming Consistency3/5
All names share the ae_ prefix and snake_case, making them readable and clearly scoped to the server. However, the set mixes verb-first names (ae_get_skill, ae_save_project, ae_render_frame), noun-first names (ae_project_export_json, ae_project_import_json), noun-info names (ae_project_info, ae_comp_info), and bare nouns (ae_catalog, ae_context, ae_do), so there is no single consistent verb_noun pattern.
Tool Count5/5
12 tools is a well-scoped size for an After Effects bridge. It covers read-only inspection, rendering, persistence, JSON round-tripping, capability discovery, and generic atomic execution without bloating the surface or leaving it feeling thin.
Completeness4/5
The core lifecycle is well covered: project/comp/layer inspection, save, frame rendering, full project export/import, and dynamic atomic operations via ae_catalog/ae_do. The main gaps are a few direct conveniences like explicit project open/close or a standalone undo tool, though ae_do's undo-group contract mitigates this.
Maintenance
ActivityMaintained
ResponsivenessNo issues