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

package/dist/index.js

@@ -2,12 +2,102 @@
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { createServer } from "./server.js";
 import { cleanupTempDir, getTempDir } from "./bridge/file-bridge.js";
+import { checkLicense } from "./license.js";
 import { execSync } from "child_process";
 import { fileURLToPath } from "url";
 import path from "path";
+import { existsSync, mkdirSync, writeFileSync, unlinkSync } from "fs";
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
 const projectRoot = path.resolve(__dirname, "..");
+// ---------------------------------------------------------------------------
+// --doctor — standalone diagnostics, no MCP client or Premiere Pro required
+// to run it. Prints a PASS/WARN/FAIL summary and exits 1 if anything failed,
+// so it's also usable in a script (`premiere-mcp --doctor || echo "broken"`).
+// Defined before the flag-handling block below since it's called from there.
+// ---------------------------------------------------------------------------
+const GREEN = "\x1b[32m";
+const RED = "\x1b[31m";
+const YELLOW = "\x1b[33m";
+const DIM = "\x1b[2m";
+const RESET = "\x1b[0m";
+function printCheck(result, label, detail) {
+    const icon = result === "pass" ? `${GREEN}✓${RESET}` : result === "warn" ? `${YELLOW}!${RESET}` : `${RED}✗${RESET}`;
+    console.log(`  ${icon} ${label}${detail ? `\n      ${DIM}${detail}${RESET}` : ""}`);
+}
+function premiereInstallCandidates() {
+    const years = ["2026", "2025", "2024", "2023", "2022"];
+    if (process.platform === "darwin") {
+        return years.map((y) => `/Applications/Adobe Premiere Pro ${y}/Adobe Premiere Pro ${y}.app`);
+    }
+    return years.map((y) => `C:\\Program Files\\Adobe\\Adobe Premiere Pro ${y}\\Adobe Premiere Pro.exe`);
+}
+// Returns whether any check failed — the caller sets process.exitCode rather
+// than us calling process.exit() here. On Windows, forcing process.exit()
+// immediately after an in-flight fetch/AbortController teardown (the live
+// license check below) can crash with a libuv assertion
+// ("UV_HANDLE_CLOSING", src/win/async.c) before the process actually exits.
+// Setting exitCode and letting the event loop drain naturally avoids it.
+async function runDoctor() {
+    console.log(`\n${DIM}premiere-mcp doctor — checking your setup${RESET}\n`);
+    let hasFail = false;
+    // 1. Node version
+    const nodeMajor = parseInt(process.version.slice(1).split(".")[0], 10);
+    if (nodeMajor >= 18) {
+        printCheck("pass", `Node.js ${process.version}`);
+    }
+    else {
+        hasFail = true;
+        printCheck("fail", `Node.js ${process.version}`, "Requires Node 18 or newer — update from nodejs.org");
+    }
+    // 2. OS (informational — both are supported, this just confirms detection)
+    const osLabel = process.platform === "darwin" ? "macOS" : process.platform === "win32" ? "Windows" : process.platform;
+    printCheck(process.platform === "darwin" || process.platform === "win32" ? "pass" : "warn", `OS: ${osLabel}`);
+    // 3. Premiere Pro install detected on disk
+    const found = premiereInstallCandidates().find((p) => existsSync(p));
+    if (found) {
+        printCheck("pass", "Premiere Pro detected", found);
+    }
+    else {
+        printCheck("warn", "Premiere Pro not found in the usual install location", "Not fatal — the MCP server only needs Premiere Pro running when a tool actually calls it.");
+    }
+    // 4. License key present
+    const licenseKey = process.env.PREMIERE_PRO_MCP_LICENSE;
+    if (!licenseKey) {
+        hasFail = true;
+        printCheck("fail", "PREMIERE_PRO_MCP_LICENSE not set", "Add it to your MCP client config (claude_desktop_config.json or equivalent).");
+    }
+    else {
+        printCheck("pass", `License key present (${licenseKey.slice(0, 8)}...)`);
+        // 5. Live validation against synthetic.com.ar (also exercises network reachability)
+        const result = await checkLicense();
+        if (result.valid) {
+            printCheck("pass", "License validates", result.expiresAt ? `Expires: ${result.expiresAt}` : "No expiration");
+        }
+        else {
+            hasFail = true;
+            printCheck("fail", "License validation failed", result.message ?? "Unknown reason");
+        }
+    }
+    // 6. Bridge temp directory writable
+    const tempDir = getTempDir();
+    try {
+        if (!existsSync(tempDir))
+            mkdirSync(tempDir, { recursive: true, mode: 0o700 });
+        const probe = path.join(tempDir, `.doctor-probe-${Date.now()}`);
+        writeFileSync(probe, "ok");
+        unlinkSync(probe);
+        printCheck("pass", "Bridge temp directory writable", tempDir);
+    }
+    catch (err) {
+        hasFail = true;
+        printCheck("fail", "Bridge temp directory not writable", `${tempDir} — ${err instanceof Error ? err.message : String(err)}`);
+    }
+    console.log(hasFail
+        ? `\n${RED}Some checks failed.${RESET} Fix the items above, or share this output with support at https://synthetic.com.ar/dashboard/support\n`
+        : `\n${GREEN}Everything looks good.${RESET}\n`);
+    return hasFail;
+}
 // Handle CLI flags
 const args = process.argv.slice(2);
 if (args.includes("--help") || args.includes("-h")) {
@@ -16,6 +106,7 @@ premiere-pro-mcp — MCP server for Adobe Premiere Pro (437 tools)
 
 Usage:
   premiere-pro-mcp              Start the MCP server (stdio transport)
+  premiere-pro-mcp --doctor        Check your setup (Node, license, Premiere Pro, temp dir)
   premiere-pro-mcp --install-cep   Install the CEP plugin into Premiere Pro
   premiere-pro-mcp --help          Show this help message
   premiere-pro-mcp --version       Show version
@@ -33,6 +124,12 @@ if (args.includes("--version") || args.includes("-v")) {
     console.log(pkg.default.version);
     process.exit(0);
 }
+let ranAsFlag = false;
+if (args.includes("--doctor")) {
+    const hasFail = await runDoctor();
+    process.exitCode = hasFail ? 1 : 0;
+    ranAsFlag = true;
+}
 if (args.includes("--install-cep")) {
     const scriptPath = path.join(projectRoot, "scripts", "install-cep.sh");
     console.log("Installing CEP plugin...\n");
@@ -63,8 +160,10 @@ async function main() {
     await server.connect(transport);
     console.error(`[premiere-pro-mcp] Server connected and ready`);
 }
-main().catch((err) => {
-    console.error("[premiere-pro-mcp] Fatal error:", err);
-    process.exit(1);
-});
+if (!ranAsFlag) {
+    main().catch((err) => {
+        console.error("[premiere-pro-mcp] Fatal error:", err);
+        process.exit(1);
+    });
+}
 //# sourceMappingURL=index.js.map

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.