@engine-room/after-effects-mcp 0.2.1 → 0.3.0

package/README.md

@@ -222,7 +222,7 @@ If you forget the second step, nothing breaks silently: the next thing you ask f
 ---
 
 <details>
-<summary><b>🧰 All 67 tools</b></summary>
+<summary><b>🧰 All 70 tools</b></summary>
 
 <br>
 
@@ -240,6 +240,8 @@ If you forget the second step, nothing breaks silently: the next thing you ask f
 | Markers (2) | `add_marker`, `remove_marker` |
 | Vision (2) | `screenshot_frame`, `screenshot_layer` |
 | Batch (1) | `run_batch` |
+| Footage (2) | `import_footage`, `create_footage_layer` |
+| Motion Graphics (1) | `export_mogrt` — export a comp as a `.mogrt` template for Premiere |
 | Explore (2) | `get_project_summary`, `find_layers` |
 | Raw (1) | `run_jsx` |
 | House style (2) | `get_house_style`, `set_house_style` |
@@ -253,6 +255,8 @@ A few behave differently from the rest:
 - **`get_layer_full`** returns a layer's transforms with their keyframes and expressions, every effect with every parameter, masks, markers and visible bounds — in one call.
 - **`run_batch`** runs many operations in a single pass and counts as one undo step. Long batches stream progress.
 - **`screenshot_frame`** and **`screenshot_layer`** are for occasional checks, not for reviewing motion frame by frame. On large comps, `downsample: 2` renders at half resolution.
+- **`import_footage`** checks what After Effects actually produced. An SVG whose `viewBox` asks for one shape and imports at another is a known After Effects bug that renders as nothing at all, with no error — so the import is refused and explained rather than left to fail silently later.
+- **`export_mogrt`** writes a Motion Graphics template for Premiere. It suppresses the modal dialogs that would otherwise sit there waiting for a click, and can set the thumbnail from any frame you choose, rather than the first one — which is usually black if the comp fades up.
 - **`run_jsx`** runs arbitrary ExtendScript for anything the other tools don't cover.
 - **`ae_guide`** is how the assistant reads its own working guidance — the same text this server publishes as MCP resources and ships to Claude Code as skills.
 
@@ -268,6 +272,7 @@ Start here: **ask your assistant to check the After Effects setup.** It reports
 | Symptom | Cause and fix |
 |---|---|
 | "Cannot reach the After Effects panel" | After Effects isn't running, or the panel isn't installed. Ask it to set up After Effects; if AE was closed, just open it afterwards. |
+| "The panel did not answer within 120 seconds" | Not the same thing. After Effects is busy — usually a long script, or a dialog waiting for a click behind another window. Wait a minute and check again before restarting anything; it normally comes back on its own. |
 | "The After Effects panel is out of date" | The tools were updated but the panel wasn't. Ask it to update the panel, then restart AE. |
 | "…updated on disk, but After Effects is still running the previous version" | The update landed; AE just hasn't restarted. Quit and reopen it. Updating again won't help. |
 | Panel never loads, but setup looks correct | On macOS, reboot once. Some builds cache the Adobe setting until a restart. |
@@ -276,6 +281,20 @@ Start here: **ask your assistant to check the After Effects setup.** It reports
 | Style guide can't be saved | The After Effects project has never been saved. Save it, then try again. |
 | You need the panel's own log | In After Effects: **Window → Extensions → AE MCP Bridge**. |
 
+**If your work legitimately takes longer.** A heavy render or a deliberately long script can pass the limit honestly. Set `AE_MCP_OP_TIMEOUT_MS` in the server's environment to a larger number of milliseconds and it applies to every operation:
+
+```json
+{
+  "mcpServers": {
+    "after-effects": {
+      "command": "npx",
+      "args": ["-y", "@engine-room/after-effects-mcp"],
+      "env": { "AE_MCP_OP_TIMEOUT_MS": "600000" }
+    }
+  }
+}
+```
+
 **The issue notebook.** These tools have rough edges. When your assistant hits one and works out a way around it, it writes the problem and the fix into `.ae-mcp/issues/` in your project folder — plain text files you can read or delete. The next session reads that notebook before guessing. The folder keeps itself out of version control.
 
 **Reporting a bug.** If the problem looks like ours rather than yours, you'll be offered the chance to pass it on, or you can start it yourself with `/report-ae-issue`. It writes the report, shows it to you, and only sends it once you say yes. Nothing about your own work — comp names, file paths, clients — goes into it. Sending needs the [GitHub CLI](https://cli.github.com); without it you get a prefilled link to click.