premiere-pro-mcp 1.8.0 → 1.9.0

package/CHANGELOG.md

@@ -6,6 +6,33 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [1.9.0] - 2026-08-02
+
+### Added
+
+- Added a read-only `verify_premiere_connection` tool, human-readable `--doctor`
+  diagnostics, and a privacy-sanitized `--support-bundle` for guided recovery.
+- Added an accessible in-panel Connection Center and native Windows/macOS CEP
+  installer pipelines that require trusted platform signing for production use.
+- Added deterministic direct and Marketplace-channel UXP CCX packaging with
+  explicit Adobe identity and live-host verification gates.
+
+### Changed
+
+- Reworked onboarding around the AI assistant an editor already uses, with the
+  Claude Desktop MCPB route first and npm/JSON configuration under Advanced.
+- Upgraded the Claude Desktop bundle manifest to MCPB v0.4 and stopped emitting
+  an unsupported `.dxt` copy of the same bytes.
+- Registered 280 core tools, exposed 278 under the default profile, and exposed
+  297 tools when the 19 capability-gated UXP tools are connected.
+
+### Validation
+
+- Automated checks cover distribution schemas, deterministic CCX packaging,
+  support-bundle privacy, installer path containment, production signing gates,
+  and connection evidence states. Real Premiere host verification and external
+  Adobe/Anthropic approvals remain separate release gates.
+
 ## [1.8.0] - 2026-08-01
 
 ### Added

package/README.md

@@ -6,7 +6,7 @@
 
 **Give AI full control over Adobe Premiere Pro.**
 
-279 core tools across 31 modules, 3 resources, and 4 guided workflows. A connected UXP host adds 19 capability-gated tools.
+280 core tools across 31 modules, 3 resources, and 4 guided workflows. A connected UXP host adds 19 capability-gated tools.
 
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 [![Node.js](https://img.shields.io/badge/Node.js-20.19%2B-green.svg)](https://nodejs.org)
@@ -27,9 +27,22 @@ An [MCP (Model Context Protocol)](https://modelcontextprotocol.io) server that l
 "Add the B-roll clips to V2, apply a cross dissolve between each, color correct them to match the A-roll, and export a 1080p ProRes."
 ```
 
-The AI handles the entire workflow through 279 core tools spanning the supported ExtendScript, QE DOM, local media analysis, and safe edit-planning surfaces. A compatible, authenticated UXP panel adds 19 documented, capability-gated workflows without replacing the production CEP bridge.
+The AI handles the entire workflow through 280 core tools spanning the supported ExtendScript, QE DOM, local media analysis, safe edit-planning, and connection-verification surfaces. A compatible, authenticated UXP panel adds 19 documented, capability-gated workflows without replacing the production CEP bridge.
 
-### What's new in 1.8.0
+### What's new in 1.9.0
+
+- **Assistant-first setup:** Claude Desktop users start with a validated MCPB
+  bundle, while npm and manual JSON configuration stay under Advanced setup.
+- **Safe connection help:** `verify_premiere_connection`, `--doctor`, the CEP
+  Connection Center, and sanitized support bundles explain exactly what is
+  installed, configured, connected, and live-verified.
+- **Distribution foundations:** MCPB v0.4, deterministic direct/Marketplace CCX
+  packaging, and native Windows/macOS CEP installer pipelines make the supported
+  routes easier to package without overstating signing or Marketplace approval.
+- **Canonical tool surface:** 280 registered tools, 278 in the default profile,
+  and 297 while the 19 capability-gated UXP tools are connected.
+
+### Previous release: 1.8.0
 
 - **Native transcript planning:** compatible UXP hosts can export and search the
   transcript Premiere generated for a clip, then preview a revision-locked set of
@@ -40,7 +53,7 @@ The AI handles the entire workflow through 279 core tools spanning the supported
 - **19 connected UXP tools:** the capability-gated UXP surface grows from 16 to 19
   without changing the 279 core-tool surface.
 
-### Previous release: 1.7.0
+### Earlier release: 1.7.0
 
 - **Six documented workflows:** compatible 26.3+ hosts can expose UXP track renaming, subclip creation, stable marker IDs, Source Monitor seeking, transcript presence checks, and AAF export.
 - **Capability first:** a tool is discoverable only with the authenticated local panel; the panel's live `capabilities.get` response—not package metadata—decides whether the current host supports it.
@@ -58,7 +71,24 @@ The AI handles the entire workflow through 279 core tools spanning the supported
 
 ## Quick Start
 
-### Before you begin
+### Easiest supported path: Claude Desktop
+
+1. Download the current [Claude Desktop bundle (`.mcpb`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.9.0/premiere-pro-mcp-1.9.0.mcpb).
+2. In Claude Desktop, open **Settings > Extensions > Advanced settings > Install Extension**, select the downloaded bundle, and restart Claude Desktop.
+3. Download the separate [signed Premiere connector (`.zxp`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.9.0/MCPBridgeCEP.zxp). Open it with your trusted ZXP installer. If your computer has no ZXP installer, use the npm connector installer in **Advanced setup** below.
+4. Restart Premiere, open a project, then open **Window > Extensions > MCP Bridge**.
+5. In Claude, enter: `Safely check my Premiere connection with verify_premiere_connection. Make no changes.`
+
+The Claude bundle contains the local MCP server, so this route does not require Node.js. The Premiere connector is a separate required install. The first prompt is read-only and reports whether the server is installed, configured, connected, and live-verified.
+
+### Other AI assistants
+
+Cursor, VS Code/Copilot, Windsurf, and other MCP clients do not currently have a project-provided one-click installer. Use their MCP settings with the advanced npm route below. Keep the assistant, server, connector, and Premiere on the same computer.
+
+<details>
+<summary><strong>Advanced setup: npm or source</strong></summary>
+
+#### Before you begin
 
 - Node.js **20.19 or newer** on Windows or macOS.
 - Adobe Premiere Pro **2020–2026**. Keep Premiere, the CEP bridge, and your MCP client on the same computer for the recommended local setup.
@@ -66,9 +96,9 @@ The AI handles the entire workflow through 279 core tools spanning the supported
   (`brew install ffmpeg` on macOS or `winget install Gyan.FFmpeg` on Windows).
   The production Docker image already includes it.
 
-### 1. Install
+#### 1. Install
 
-**Option A — npm (recommended):**
+**Option A — npm:**
 
 ```bash
 npm install -g premiere-pro-mcp
@@ -83,7 +113,7 @@ npm install
 npm run build
 ```
 
-### 2. Install the CEP plugin
+#### 2. Install the CEP plugin
 
 **If installed via npm:**
 
@@ -99,6 +129,16 @@ npm run install-cep
 
 This installs the plugin into Premiere Pro's per-user extensions folder and enables debug mode.
 
+#### 3. Check the setup
+
+```bash
+premiere-pro-mcp --doctor
+```
+
+Then ask your MCP client to run `verify_premiere_connection`. The check is read-only.
+
+</details>
+
 ---
 
 ## Publishing to npm
@@ -259,11 +299,11 @@ From a clone of this repository:
 ```bash
 codex plugin marketplace add .
 codex plugin add premiere-pro@premiere-pro-mcp
-npx -y premiere-pro-mcp@1.8.0 --install-cep
+npx -y premiere-pro-mcp@1.9.0 --install-cep
 ```
 
 Restart Premiere Pro and start a new Codex session after installation. The plugin
-launches `premiere-pro-mcp@1.8.0` through `npx`; the separate CEP installation is
+launches `premiere-pro-mcp@1.9.0` through `npx`; the separate CEP installation is
 required because the MCP server communicates with the running Premiere host through
 the local bridge.
 
@@ -283,15 +323,15 @@ For Claude Code, add this repository as a marketplace and install the plugin:
 Then install the Premiere bridge and start a new Claude Code session:
 
 ```bash
-npx -y premiere-pro-mcp@1.8.0 --install-cep
+npx -y premiere-pro-mcp@1.9.0 --install-cep
 ```
 
 The Claude Code package lives in
 [`claude-plugins/premiere-pro`](claude-plugins/premiere-pro), with its marketplace
 at [`.claude-plugin/marketplace.json`](.claude-plugin/marketplace.json).
 
-Claude Desktop uses the self-contained MCP Bundle format, formerly called Desktop
-Extensions. Build both the current `.mcpb` artifact and a legacy `.dxt` copy with:
+Claude Desktop uses the self-contained MCP Bundle (`.mcpb`) format. Build and
+validate the current bundle with:
 
 ```bash
 npm run build:claude
@@ -322,7 +362,7 @@ installed separately.
 QE-backed tools are reported as `experimental` because QE is undocumented and can vary between Premiere builds. Authority availability is reported separately from implementation support, so disabling `edit`, for example, does not incorrectly label editing tools as unsupported. Static metadata never claims that a Premiere operation succeeded; use `ping` and inspect each tool result for runtime evidence.
 
 MCP `tools/list` is filtered to the active authority profile. The default
-`inspect,edit,export,filesystem` profile advertises 277 of the 279 registered
+`inspect,edit,export,filesystem` profile advertises 278 of the 280 registered
 tools and omits `execute_extendscript` and `evaluate_expression`, which require
 explicit `unsafe-script` authority. `ping` and `get_capabilities` remain visible
 under every profile so a restricted or misconfigured server can still explain
@@ -437,7 +477,7 @@ The file-based IPC bridge is simple, reliable, and works across macOS and Window
 
 ---
 
-## Tools (279 core total; 277 under the default profile; 296 with a connected UXP bridge)
+## Tools (280 core total; 278 under the default profile; 297 with a connected UXP bridge)
 
 ### Discovery & Inspection (10 + 10)
 
@@ -680,7 +720,7 @@ premiere-pro-mcp/
 ├── src/
 │   ├── index.ts                 # Entry point — stdio transport setup
 │   ├── http-server.ts           # Entry point — HTTP/SSE transport (Fly.io / remote)
-│   ├── server.ts                # MCP server — registers 279 core tools, filtered by authority profile
+│   ├── server.ts                # MCP server — registers 280 tools, filtered by authority profile
 │   ├── bridge/
 │   │   ├── file-bridge.ts       # File-based IPC (write .jsx, poll .json)
 │   │   └── script-builder.ts    # ExtendScript generator with ES3 helpers

package/cep-plugin/CSXS/manifest.xml

@@ -1,8 +1,8 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<ExtensionManifest Version="7.0" ExtensionBundleId="com.mcp.premiere.bridge" ExtensionBundleVersion="1.8.0" ExtensionBundleName="MCP Bridge">
+<ExtensionManifest Version="7.0" ExtensionBundleId="com.mcp.premiere.bridge" ExtensionBundleVersion="1.9.0" ExtensionBundleName="MCP Bridge">
   <ExtensionList>
-    <Extension Id="com.mcp.premiere.bridge.panel" Version="1.8.0"/>
-    <Extension Id="com.mcp.premiere.bridge.headless" Version="1.8.0"/>
+    <Extension Id="com.mcp.premiere.bridge.panel" Version="1.9.0"/>
+    <Extension Id="com.mcp.premiere.bridge.headless" Version="1.9.0"/>
   </ExtensionList>
   <ExecutionEnvironment>
     <HostList>

package/cep-plugin/index.html

@@ -19,12 +19,12 @@
 
     <section class="status-panel" role="status" aria-live="polite" aria-atomic="true">
       <div class="status-indicator" aria-hidden="true">
-        <div class="status-ring"><div class="status-dot connected" id="statusDot"></div></div>
+        <div class="status-ring"><div class="status-dot waiting" id="statusDot"></div></div>
       </div>
       <div class="status-copy">
         <span class="section-label">Bridge status</span>
-        <strong id="statusText">Connected</strong>
-        <span id="statusDetail">Premiere Pro link is active</span>
+        <strong id="statusText">Starting connector…</strong>
+        <span id="statusDetail">Checking Premiere Pro</span>
       </div>
       <div class="command-stat">
         <strong id="cmdCount">0</strong>
@@ -32,6 +32,22 @@
       </div>
     </section>
 
+    <section class="connection-center" aria-labelledby="connectionCenterTitle">
+      <div class="section-heading">
+        <div>
+          <span class="section-label">Connection Center</span>
+          <h2 id="connectionCenterTitle">Ready-to-edit check</h2>
+        </div>
+        <button class="save-link" type="button" onclick="refreshConnectionCenter()" aria-controls="connectionChecks">Refresh</button>
+      </div>
+      <p class="connection-intro">This panel only checks Premiere. In your AI assistant, run <strong>Verify Premiere connection</strong> for the complete safe check.</p>
+      <ul class="connection-checks" id="connectionChecks">
+        <li id="checkConnector" data-state="waiting"><span class="check-dot" aria-hidden="true"></span><span><strong>Connector</strong><small>Starting…</small></span></li>
+        <li id="checkProject" data-state="waiting"><span class="check-dot" aria-hidden="true"></span><span><strong>Project</strong><small>Checking…</small></span></li>
+        <li id="checkSequence" data-state="waiting"><span class="check-dot" aria-hidden="true"></span><span><strong>Active sequence</strong><small>Checking…</small></span></li>
+      </ul>
+    </section>
+
     <section class="config-section">
       <div class="section-heading">
         <div>
@@ -65,7 +81,7 @@
     <section class="update-section" aria-live="polite">
       <div class="update-copy">
         <span class="section-label">Connector updates</span>
-        <strong id="updateTitle">Version 1.8.0</strong>
+        <strong id="updateTitle">Version 1.9.0</strong>
         <span id="updateDetail">Checking for updates…</span>
       </div>
       <button id="btnUpdate" class="button button-update" onclick="handleUpdateClick()" type="button" disabled>

package/cep-plugin/main.js

@@ -32,12 +32,47 @@ function setStatus(state, text) {
   var detail = document.getElementById("statusDetail");
   if (detail) {
     if (state === "connected") detail.textContent = "Premiere Pro link is active";
-    else if (state === "waiting") detail.textContent = "Ready to accept commands";
+    else if (state === "waiting") detail.textContent = "Ready for an AI assistant connection";
     else if (state === "error") detail.textContent = "Bridge needs attention";
     else detail.textContent = "Waiting for Premiere Pro";
   }
 }
 
+function setConnectionCheck(id, state, detail) {
+  var el = document.getElementById(id);
+  if (!el) return;
+  el.setAttribute("data-state", state);
+  var text = el.getElementsByTagName("small")[0];
+  if (text) text.textContent = detail;
+}
+
+// This reads only boolean Premiere state. Do not put project names, paths, or
+// media information in the panel: the MCP safe-check uses the same boundary.
+function refreshConnectionCenter() {
+  if (!bridgeRunning) {
+    setConnectionCheck("checkConnector", "waiting", "Start the connector first");
+    setConnectionCheck("checkProject", "waiting", "Waiting for the connector");
+    setConnectionCheck("checkSequence", "waiting", "Waiting for the connector");
+    return;
+  }
+  setConnectionCheck("checkConnector", "ready", "Running in Premiere Pro");
+  setConnectionCheck("checkProject", "waiting", "Checking…");
+  setConnectionCheck("checkSequence", "waiting", "Checking…");
+  cs.evalScript(
+    '(function(){var p=app&&app.project;return JSON.stringify({projectOpen:!!(p&&typeof p.name!=="undefined"),sequenceOpen:!!(p&&p.activeSequence)});}())',
+    function (raw) {
+      try {
+        var state = JSON.parse(raw || "{}");
+        setConnectionCheck("checkProject", state.projectOpen ? "ready" : "needs-attention", state.projectOpen ? "Project open" : "Open a project in Premiere Pro");
+        setConnectionCheck("checkSequence", state.sequenceOpen ? "ready" : "needs-attention", state.sequenceOpen ? "Active sequence open" : "Open a sequence in Premiere Pro");
+      } catch (e) {
+        setConnectionCheck("checkProject", "needs-attention", "Could not read Premiere state");
+        setConnectionCheck("checkSequence", "needs-attention", "Could not read Premiere state");
+      }
+    }
+  );
+}
+
 // ---- File I/O via Node.js (CEP has access to Node) ----
 // --enable-nodejs puts `require` in the global scope on most hosts, but on some it
 // lands on cep_node instead. Try both, and fail loudly rather than letting fs come
@@ -214,20 +249,13 @@ function startBridge() {
 
   ensureDir(tempDir);
   bridgeRunning = true;
-  setStatus("connected", "Running — polling " + tempDir);
-  log("Bridge started. Temp dir: " + tempDir);
+  setStatus("waiting", "Connector running");
+  log("Connector started and ready for safe checks.", "ok");
 
   document.getElementById("btnStart").disabled = true;
   document.getElementById("btnStop").disabled = false;
 
-  // Verify Premiere Pro connection
-  cs.evalScript("app.version", function (version) {
-    if (version && version !== "undefined") {
-      log("Premiere Pro: " + version, "ok");
-    } else {
-      log("Warning: Could not detect Premiere Pro version", "err");
-    }
-  });
+  refreshConnectionCenter();
 
   pollInterval = setInterval(function () {
     if (bridgeRunning) processCommands();
@@ -240,6 +268,7 @@ function stopBridge() {
   pollInterval = null;
 
   setStatus("", "Stopped");
+  refreshConnectionCenter();
   log("Bridge stopped");
 
   document.getElementById("btnStart").disabled = false;

package/cep-plugin/styles.css

@@ -197,6 +197,27 @@ button { -webkit-appearance: none; }
   border-radius: var(--radius);
   background: var(--surface);
 }
+
+.connection-center {
+  margin: 0 0 14px;
+  padding: 12px;
+  border: 1px solid var(--border);
+  border-radius: var(--radius);
+  background: var(--surface);
+}
+.connection-center .section-heading { margin-bottom: 8px; }
+.connection-center h2 { font-size: 12px; }
+.connection-intro { margin: 0 0 10px; color: var(--text-muted); font-size: 9px; line-height: 1.45; }
+.connection-intro strong { color: var(--text-secondary); font-weight: 600; }
+.connection-checks { display: grid; gap: 6px; padding: 0; margin: 0; list-style: none; }
+.connection-checks li { display: flex; align-items: center; gap: 8px; min-height: 34px; padding: 6px 8px; border: 1px solid var(--border); border-radius: 5px; background: var(--surface-deep); }
+.connection-checks li > span:last-child { min-width: 0; }
+.connection-checks strong, .connection-checks small { display: block; }
+.connection-checks strong { color: var(--text-secondary); font-size: 10px; font-weight: 600; }
+.connection-checks small { margin-top: 2px; color: var(--text-muted); font-size: 9px; }
+.check-dot { width: 7px; height: 7px; flex: 0 0 auto; border-radius: 50%; background: var(--text-muted); }
+.connection-checks li[data-state="ready"] .check-dot { background: var(--green); box-shadow: 0 0 0 3px var(--green-soft); }
+.connection-checks li[data-state="needs-attention"] .check-dot { background: var(--amber); }
 .update-copy { min-width: 0; flex: 1; }
 .update-copy strong, .update-copy > span:last-child { display: block; }
 .update-copy strong { font-size: 11px; font-weight: 600; }

package/cep-plugin/updater.cjs

@@ -7,7 +7,7 @@
 })(this, function () {
   "use strict";
 
-  var CURRENT_VERSION = "1.8.0";
+  var CURRENT_VERSION = "1.9.0";
   var LATEST_RELEASE_API =
     "https://api.github.com/repos/leancoderkavy/premiere-pro-mcp/releases/latest";
   var RELEASES_URL =

package/dist/diagnostics.d.ts

@@ -0,0 +1,85 @@
+/**
+ * A readiness boundary says what was actually established. It deliberately
+ * does not turn an installed connector into a claim that Premiere is live.
+ */
+export type ReadinessBoundary = "installed" | "configured" | "connected" | "live_verified";
+export type ReadinessState = "ready" | "needs_attention" | "not_checked";
+export interface ReadinessComponent {
+    id: "mcp_process" | "premiere_connector" | "premiere_host" | "active_project" | "active_sequence" | "uxp_bridge";
+    label: string;
+    boundary: ReadinessBoundary;
+    state: ReadinessState;
+    message: string;
+    repair?: string;
+}
+export interface LocalDoctorReport {
+    schemaVersion: "premiere-pro-mcp.doctor.v1";
+    generatedAt: string;
+    runtime: {
+        platform: NodeJS.Platform;
+        nodeMajor: number | null;
+    };
+    overall: "ready" | "needs_attention";
+    components: ReadinessComponent[];
+    privacy: {
+        includes: string[];
+        excludes: string[];
+    };
+}
+export interface FirstRunReport {
+    schemaVersion: "premiere-pro-mcp.first-run.v1";
+    safeCheck: {
+        readOnly: true;
+        mutatesProject: false;
+        verificationScope: "mcp_process_premiere_host_active_project_active_sequence";
+    };
+    backend: "cep" | "uxp";
+    overall: "ready" | "needs_attention";
+    components: ReadinessComponent[];
+    nextStep: string;
+    repair?: string;
+}
+export interface SupportBundle {
+    schemaVersion: "premiere-pro-mcp.support-bundle.v1";
+    generatedAt: string;
+    application: {
+        version: string;
+        nodeMajor: number | null;
+        platform: NodeJS.Platform;
+        architecture: string;
+    };
+    doctor: LocalDoctorReport;
+    privacy: {
+        excludes: string[];
+    };
+}
+export interface LocalDoctorOptions {
+    platform?: NodeJS.Platform;
+    architecture?: string;
+    nodeVersion?: string;
+    environment?: NodeJS.ProcessEnv;
+    now?: () => Date;
+    exists?: (file: string) => boolean;
+}
+export interface SupportBundleOptions extends LocalDoctorOptions {
+    version: string;
+}
+export interface FirstRunHostState {
+    reachable: boolean;
+    projectOpen?: boolean;
+    sequenceOpen?: boolean;
+}
+/**
+ * Inspect local install/configuration facts only. The report intentionally
+ * cannot imply that Premiere is open or that an MCP client has connected.
+ */
+export declare function collectLocalDoctor(options?: LocalDoctorOptions): LocalDoctorReport;
+/** Build a first-run report from a sanitized host response. No names or paths enter this contract. */
+export declare function buildFirstRunReport(backend: "cep" | "uxp", host: FirstRunHostState): FirstRunReport;
+/**
+ * Produce a safe attachment for support. It is deliberately a status snapshot,
+ * not a log collector: logs commonly contain project names, local paths, or tokens.
+ */
+export declare function createSupportBundle(options: SupportBundleOptions): SupportBundle;
+export declare function renderDoctorHuman(report: LocalDoctorReport): string;
+//# sourceMappingURL=diagnostics.d.ts.map