@synthetic-ai/premiere-mcp 2.2.0 → 2.3.0-dev.0

package/dist/license.js

@@ -3,9 +3,45 @@
  * Same pattern as ae-mcp/src/server.mjs and photoshop-mcp/server.mjs:
  * validate once, cache for an hour, let diagnostic tools through for free.
  */
+import os from "node:os";
+import fs from "node:fs";
+import path from "node:path";
+import crypto from "node:crypto";
 const LICENSE_KEY = process.env.PREMIERE_PRO_MCP_LICENSE;
 const LICENSE_VALIDATION_URL = "https://synthetic.com.ar/api/v1/license/validate";
 const LICENSE_CACHE_TTL_MS = 60 * 60 * 1000; // 1 hour
+// Device identity (for the 2-device license cap) — shared across all
+// Synthetic MCP packages on purpose: one physical machine should count as
+// ONE device against the cap, not one per product installed on it. See
+// photoshop-mcp/server.mjs's getMachineId() for the identical logic.
+function getMachineId() {
+    try {
+        const dir = path.join(os.homedir(), ".synthetic");
+        const file = path.join(dir, "device-id");
+        if (fs.existsSync(file)) {
+            const id = fs.readFileSync(file, "utf8").trim();
+            if (id)
+                return id;
+        }
+        fs.mkdirSync(dir, { recursive: true });
+        const id = crypto.randomUUID();
+        fs.writeFileSync(file, id, "utf8");
+        return id;
+    }
+    catch {
+        return "volatile-" + crypto.randomUUID();
+    }
+}
+function getDeviceLabel() {
+    try {
+        return `${os.hostname()} (${process.platform})`;
+    }
+    catch {
+        return null;
+    }
+}
+const MACHINE_ID = getMachineId();
+const DEVICE_LABEL = getDeviceLabel();
 let cache = null;
 async function postJson(url, body) {
     try {
@@ -41,6 +77,8 @@ export async function checkLicense() {
         const result = await postJson(LICENSE_VALIDATION_URL, {
             key: LICENSE_KEY,
             product: "premiere-mcp",
+            machineId: MACHINE_ID,
+            deviceLabel: DEVICE_LABEL,
         });
         if (result) {
             cache = { ...result, checkedAt: Date.now() };

package/dist/server.js

@@ -38,66 +38,66 @@ import { getSequenceSettingsTools } from "./tools/sequence-settings.js";
 import { EXTENDSCRIPT_REFERENCE } from "./resources/extendscript-reference.js";
 import { checkLicense, licenseErrorResponse, FREE_TOOLS } from "./license.js";
 import { z } from "zod";
-const PREMIERE_INSTRUCTIONS = `You are controlling Adobe Premiere Pro through MCP tools. Follow these best practices:
-
-WORKFLOW ORDER:
-1. Always call get_project_info first to understand the current state.
-2. Import media before adding to timeline.
-3. Create/select a sequence before timeline operations.
-4. Add clips first, then effects, then transitions.
-5. Save the project after making significant changes.
-
-TIMELINE RULES:
-- Clips are identified by node_id. Use get_active_sequence or list_sequence_tracks to discover node IDs.
-- Video clips on higher track indices appear on top of lower ones (compositing order).
-- Images default to ~5 seconds duration when added to timeline.
-- The first clip added to a new sequence determines its resolution and frame rate.
-- Time values are in seconds (the tools handle tick conversion internally).
-
-EFFECTS & TRANSITIONS:
-- Apply effects by name using apply_effect (e.g., "Gaussian Blur", "Lumetri Color").
-- Use list_available_effects to find exact effect names.
-- Transitions require clips to be adjacent (no gap between them).
-- Keep transitions short (0.5-2 seconds typically).
-- Use color_correct for Lumetri Color adjustments rather than manual property setting.
-
-KEYFRAMES:
-- Use get_effect_properties to discover property names before setting values.
-- Enable keyframes with add_keyframe; the property auto-enables time-varying.
-- Interpolation types: "linear" (smooth), "hold" (instant jump), "bezier" (custom easing).
-
-QE DOM TOOLS:
-- Tools marked "Uses QE DOM" use an undocumented API. They are powerful but may behave unexpectedly.
-- ripple_delete, roll_edit, slide_edit, slip_edit are QE-based advanced trim tools.
-- set_clip_speed_qe is more reliable than the ExtendScript speed method.
-
-CLIPS & SELECTION:
-- Use set_clip_selection to select clips before operations that work on selection (link, unlink, scene_edit_detection).
-- Use overwrite_clip for 3-point editing (overwrites existing content).
-- Use add_to_timeline for insert editing (ripples content forward).
-
-BINS & ORGANIZATION:
-- Bins are folders in the project panel. Use create_bin, delete_bin, rename_bin.
-- Use move_item_to_bin to organize imported media.
-- create_smart_bin creates auto-populating search bins.
-
-EXPORT:
-- Use export_sequence for AME-based encoding with presets.
-- Use export_frame to capture a single frame as an image.
-- Use start_batch_encode to begin rendering all queued items.
-
-ERROR HANDLING:
-- If a tool returns "No active sequence", call set_active_sequence first.
-- If a tool returns "Clip not found", the node_id may have changed after timeline edits. Re-query the sequence.
-- If "QE clip not found", the clip index may differ between DOM and QE. Try re-querying.
-
-CUSTOM SCRIPTING:
-- Use execute_extendscript to write and run any ExtendScript code for tasks not covered by existing tools.
-- Use evaluate_expression for quick one-line queries.
-- Use inspect_dom_object to explore unfamiliar objects.
-- Use get_premiere_state as your first call to understand the full current context.
-- Use get_sequence_structure for detailed timeline layout before edits.
-- Read the "extendscript-reference" resource for the complete API cheat sheet.
+const PREMIERE_INSTRUCTIONS = `You are controlling Adobe Premiere Pro through MCP tools. Follow these best practices:
+
+WORKFLOW ORDER:
+1. Always call get_project_info first to understand the current state.
+2. Import media before adding to timeline.
+3. Create/select a sequence before timeline operations.
+4. Add clips first, then effects, then transitions.
+5. Save the project after making significant changes.
+
+TIMELINE RULES:
+- Clips are identified by node_id. Use get_active_sequence or list_sequence_tracks to discover node IDs.
+- Video clips on higher track indices appear on top of lower ones (compositing order).
+- Images default to ~5 seconds duration when added to timeline.
+- The first clip added to a new sequence determines its resolution and frame rate.
+- Time values are in seconds (the tools handle tick conversion internally).
+
+EFFECTS & TRANSITIONS:
+- Apply effects by name using apply_effect (e.g., "Gaussian Blur", "Lumetri Color").
+- Use list_available_effects to find exact effect names.
+- Transitions require clips to be adjacent (no gap between them).
+- Keep transitions short (0.5-2 seconds typically).
+- Use color_correct for Lumetri Color adjustments rather than manual property setting.
+
+KEYFRAMES:
+- Use get_effect_properties to discover property names before setting values.
+- Enable keyframes with add_keyframe; the property auto-enables time-varying.
+- Interpolation types: "linear" (smooth), "hold" (instant jump), "bezier" (custom easing).
+
+QE DOM TOOLS:
+- Tools marked "Uses QE DOM" use an undocumented API. They are powerful but may behave unexpectedly.
+- ripple_delete, roll_edit, slide_edit, slip_edit are QE-based advanced trim tools.
+- set_clip_speed_qe is more reliable than the ExtendScript speed method.
+
+CLIPS & SELECTION:
+- Use set_clip_selection to select clips before operations that work on selection (link, unlink, scene_edit_detection).
+- Use overwrite_clip for 3-point editing (overwrites existing content).
+- Use add_to_timeline for insert editing (ripples content forward).
+
+BINS & ORGANIZATION:
+- Bins are folders in the project panel. Use create_bin, delete_bin, rename_bin.
+- Use move_item_to_bin to organize imported media.
+- create_smart_bin creates auto-populating search bins.
+
+EXPORT:
+- Use export_sequence for AME-based encoding with presets.
+- Use export_frame to capture a single frame as an image.
+- Use start_batch_encode to begin rendering all queued items.
+
+ERROR HANDLING:
+- If a tool returns "No active sequence", call set_active_sequence first.
+- If a tool returns "Clip not found", the node_id may have changed after timeline edits. Re-query the sequence.
+- If "QE clip not found", the clip index may differ between DOM and QE. Try re-querying.
+
+CUSTOM SCRIPTING:
+- Use execute_extendscript to write and run any ExtendScript code for tasks not covered by existing tools.
+- Use evaluate_expression for quick one-line queries.
+- Use inspect_dom_object to explore unfamiliar objects.
+- Use get_premiere_state as your first call to understand the full current context.
+- Use get_sequence_structure for detailed timeline layout before edits.
+- Read the "extendscript-reference" resource for the complete API cheat sheet.
 `;
 /**
  * Convert a JSON Schema-style parameters object to a Zod shape for MCP SDK registration.