premiere-pro-mcp 1.13.0 → 1.14.2

package/CHANGELOG.md

@@ -6,6 +6,68 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [1.14.2] - 2026-08-28
+
+### Added
+
+- Added dual-era MCP serving with the stable TypeScript SDK v2: modern
+  `2026-07-28` discovery and stateless request handling over HTTP and stdio,
+  with legacy protocol compatibility through `2025-11-25`.
+- Added validated modern routing headers, cache hints, subscription-listen
+  support, a formal Premiere extension capability, and a machine-readable MCP
+  protocol report in `get_capabilities`.
+- Added an evidence-backed capability matrix covering implemented, SDK-ready,
+  external-boundary, deprecated, and intentionally unsupported MCP surfaces.
+
+### Changed
+
+- Migrated tool, resource, prompt, client, stdio, and Node HTTP integrations
+  from `@modelcontextprotocol/sdk` v1 to the split v2 packages and Standard
+  Schema registration APIs.
+
+### Fixed
+
+- Restored strict JSON Schema 2020-12 tool compatibility and corrected legacy
+  CEP argument contracts, Premiere Time units, Adobe Media Encoder output
+  paths, active-sequence verification, metadata readback, XMP patch merging,
+  and single-extension UXP frame exports.
+- Replaced false-success responses for structural edits, duplicate
+  consolidation, effect copying, nesting, deletion, and other host mutations
+  with verified outcomes or explicit fail-closed errors.
+- Added bounded UXP selection lift and native transition adapters while keeping
+  unavailable track-management and global-redo capabilities explicit.
+
+### Safety
+
+- Live Premiere resources remain private and uncached, and tool discovery is
+  private-cache scoped. The tasks extension and OAuth discovery are not
+  advertised without the durable storage and authorization infrastructure they
+  require.
+
+## [1.14.1] - 2026-08-27
+
+### Fixed
+
+- Made npm package verification isolate its temporary tarball and select the
+  package matching `package.json`, avoiding a current npm CLI packaging
+  regression before publication.
+
+## [1.14.0] - 2026-08-27
+
+### Added
+
+- Added focused `essential`, `inspection`, `delivery`, and `captions` tool packs
+  so compatible MCP clients can begin with a smaller task-specific catalog.
+- Added `inspect_sequence_review_report`, a read-only, handoff-oriented sequence
+  report, and explicit MCP output schemas for every registered tool.
+
+### Safety
+
+- Tool packs change discoverability, not authority. Review reports redact media
+  paths by default and include marker comments only with explicit opt-in.
+- Package and response-contract checks remain distinct from licensed Premiere
+  host verification.
+
 ## [1.13.0] - 2026-08-22
 
 ### Added

package/README.md

@@ -2,15 +2,17 @@
 
 # MCP for Adobe Premiere Pro
 
+<!-- mcp-name: io.github.leancoderkavy/premiere-pro -->
+
 [![MCP Toplist](https://mcptoplist.com/badge/glama%2Fleancoderkavy%2Fpremiere-pro-mcp.svg)](https://mcptoplist.com/server/glama%2Fleancoderkavy%2Fpremiere-pro-mcp)
 
 **Give compatible AI assistants structured control over supported Adobe Premiere Pro workflows.**
 
-288 core tools across 34 modules, 4 resources, and 11 guided workflows. A connected UXP host adds 50 capability-gated tools.
+320 core tools across 37 modules, 14 resources, and 11 guided workflows. A connected UXP host adds 54 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)
-[![MCP](https://img.shields.io/badge/MCP-1.29-purple.svg)](https://modelcontextprotocol.io)
+[![MCP](https://img.shields.io/badge/MCP-2026--07--28-purple.svg)](https://modelcontextprotocol.io/specification/2026-07-28)
 [![npm](https://img.shields.io/npm/v/premiere-pro-mcp.svg)](https://www.npmjs.com/package/premiere-pro-mcp)
 [![Fly.io](https://img.shields.io/badge/Fly.io-deployed-7C3AED.svg)](https://premiere-pro-mcp.fly.dev)
 [![Premiere Pro](https://img.shields.io/badge/Premiere%20Pro-2020--2026-9999FF.svg)](https://www.adobe.com/products/premiere.html)
@@ -29,21 +31,33 @@ 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 288 core tools spanning the supported ExtendScript, QE DOM, revisioned project-context retrieval, safe edit-planning, project-intake preview, and connection-verification surfaces. A compatible, authenticated UXP panel adds 50 documented, capability-gated tools without replacing the production CEP bridge.
+The AI handles the entire workflow through 320 core tools spanning the supported ExtendScript, QE DOM, local media and interchange analysis, revisioned project-context retrieval, safe edit-planning, project-intake preview, review handoff, and connection-verification surfaces. A compatible, authenticated UXP panel adds 54 documented, capability-gated tools without replacing the production CEP bridge.
 
-### Latest release: 1.13.0
+### Latest release: 1.14.2
 
-- **MOGRT text and graphics:** `set_effect_property` now accepts string-backed
-  parameters with safe serialization and readback status.
-- **Effect discovery clarity:** an empty legacy QE effect catalog now returns a
-  no-mutation capability response and directs connected hosts to the documented
-  UXP catalog/add workflow.
-- **Verification clarity:** property readback remains distinct from playback or
-  exported-frame verification in a licensed Premiere Pro host.
+- **Focused discovery:** compatible MCP clients can select essential,
+  inspection, delivery, or captions tool packs instead of beginning with the
+  full catalog.
+- **Review handoff:** `inspect_sequence_review_report` returns a read-only,
+  path-redacted sequence report, with marker comments only when requested.
+- **Interoperability:** all registered MCP tools now declare explicit output
+  schemas; this release does not substitute automated checks for licensed-host
+  verification.
+- **Reliable packaging:** npm package verification now isolates its temporary
+  tarball, keeping the validated distribution path compatible with the current
+  npm CLI.
 
-See the [v1.13.0 release notes](https://github.com/leancoderkavy/premiere-pro-mcp/releases/tag/v1.13.0)
+See the [v1.14.2 release notes](https://github.com/leancoderkavy/premiere-pro-mcp/releases/tag/v1.14.2)
 for complete details. Live installation in Premiere Pro still requires host verification.
 
+### Current MCP protocol support
+
+The server uses the stable TypeScript SDK v2 and serves the `2026-07-28`
+stateless protocol over HTTP and stdio, while retaining legacy MCP compatibility
+through `2025-11-25`. Modern clients receive discovery, validated routing headers,
+cache hints, subscription-stream support, and the formal Premiere extension
+capability. See the [complete MCP capability and boundary report](docs/mcp-2026-07-28-capabilities.md).
+
 ---
 
 ## For editors evaluating an AI workflow
@@ -58,20 +72,44 @@ or small test sequence.
 For product context, see the [Adobe Premiere AI Assistant and MCP comparison](https://premiere-pro-mcp.com/blog/adobe-premiere-ai-assistant-vs-mcp/)
 and the [Claude Desktop setup guide](https://premiere-pro-mcp.com/blog/claude-desktop-premiere-pro-mcp-setup/).
 
+If you are deciding between a single local project, an Adobe Production on shared
+storage, or a remote Team Project, use the [Premiere Pro collaboration workflow
+guide](https://premiere-pro-mcp.com/premiere-pro-collaboration-workflow/) before
+you evaluate an MCP path. It links the relevant Adobe guidance, makes no project
+inspection request, and ends with the same read-only connection check.
+
+For a concrete first Project Intake preview, choose one of the three
+[schema-checked, no-sensitive-data starter templates](https://premiere-pro-mcp.com/project-intake/#starter-template).
+They are evaluation samples only: a human policy owner must review and replace
+their bins, media rules, and organization rules before a facility uses one.
+
 ---
 
 ## Quick Start
 
 ### Easiest supported path: Claude Desktop
 
-1. Download the current [Claude Desktop bundle (`.mcpb`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.13.0/premiere-pro-mcp-1.13.0.mcpb).
+1. Download the current [Claude Desktop bundle (`.mcpb`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.14.2/premiere-pro-mcp-1.14.2.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.13.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.
+3. Download the separate [signed Premiere connector (`.zxp`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.14.2/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 for Adobe Premiere Pro**.
 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.
 
+### First proof, before the first edit
+
+![Illustrated local Premiere MCP workflow](landing/public/premiere-pro-mcp-demo-poster.png)
+
+*This is an illustrated workflow, not a Premiere panel screenshot or licensed-host proof.*
+
+1. Open a copied test project and an active sequence in Premiere.
+2. Open **Window > Extensions > MCP for Adobe Premiere Pro**. “Running” means the local panel bridge is available; it does not show that an edit completed.
+3. Run `premiere-pro-mcp --doctor` to check only local package/configuration readiness.
+4. Ask the AI client: `Run verify_premiere_connection. Make no changes.` The returned check is read-only and avoids project names, paths, and media details.
+
+If a bridge, project, or active sequence is missing, fix that setup state before allowing a mutation. For a concise, translatable version of this path, see [quick starts in English, Spanish, and Japanese](docs/quickstart/README.md). The translations are machine-assisted drafts and retain command names in English.
+
 ### 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.
@@ -128,6 +166,16 @@ premiere-pro-mcp --doctor
 
 Then ask your MCP client to run `verify_premiere_connection`. The check is read-only.
 
+#### Remove the CEP connector
+
+Fully quit Premiere, then remove only this connector:
+
+```bash
+premiere-pro-mcp --uninstall-cep
+```
+
+The uninstaller intentionally leaves Adobe's shared `PlayerDebugMode` setting in place so it does not disrupt other CEP extensions. Remove the MCP server from your AI client's configuration and uninstall the npm package separately if you no longer use it. On macOS, `--uninstall-cep` removes the per-user npm/source install; the signed system-wide `.pkg` route has a separate privileged removal command in [distribution readiness](docs/distribution-readiness.md#connector-removal).
+
 </details>
 
 ---
@@ -290,11 +338,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.13.0 --install-cep
+npx -y premiere-pro-mcp@1.14.2 --install-cep
 ```
 
 Restart Premiere Pro and start a new Codex session after installation. The plugin
-launches `premiere-pro-mcp@1.13.0` through `npx`; the separate CEP installation is
+launches `premiere-pro-mcp@1.14.2` through `npx`; the separate CEP installation is
 required because the MCP server communicates with the running Premiere host through
 the local bridge.
 
@@ -314,7 +362,7 @@ 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.13.0 --install-cep
+npx -y premiere-pro-mcp@1.14.2 --install-cep
 ```
 
 The Claude Code package lives in
@@ -353,13 +401,36 @@ 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 286 of the 288 registered
+`inspect,edit,export,filesystem` profile advertises 318 of the 320 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
 its state. The call-time capability guard remains authoritative even if listing
 metadata is wrong.
 
+### Workflow-scoped discovery packs and structured outputs
+
+By default, the full permitted catalog remains available. Set
+`PREMIERE_MCP_TOOL_PACKS` to `essential`, `inspection`, `delivery`, `captions`,
+or a comma-separated combination such as `inspection,captions` to reduce the
+tool discovery and registered session surface for a focused client. `full` is the explicit
+full-catalog mode and cannot be combined with another pack. `ping` and
+`get_capabilities` remain listed for diagnosis, and every registered call still
+passes through the same capability guard; a pack never grants authority.
+
+Every listed tool now declares the same machine-readable result envelope through
+MCP `outputSchema`: `ok`, `tool`, plus `data` on success or `error` on failure.
+The tool-specific `data` shape remains versioned by the individual tool result,
+so clients can reliably distinguish transport success from a Premiere or local
+operation failure without parsing the text block.
+
+`inspect_sequence_review_report` creates one read-only handoff report from
+Premiere timeline readback: sequence structure, primary-track gaps, disabled
+clips, muted tracks, marker timing, and offline-source evidence. It never
+returns media paths; marker comments are omitted unless explicitly requested.
+The report is not proof of rendered pixels, audio quality, caption accuracy,
+rights, or editorial approval.
+
 The MCP handshake reads `serverInfo.version` from the installed `package.json`,
 so clients receive the package version that is actually running rather than a
 separately maintained literal.
@@ -433,7 +504,7 @@ PREMIERE_UXP_TOKEN="replace-with-a-long-random-secret" premiere-pro-mcp
 
 Enter the same token in the UXP panel. The listener binds only to `127.0.0.1:7777`, authenticates the WebSocket upgrade, requires a versioned capability handshake, correlates concurrent requests, and fails pending work on timeout or disconnect. Set `PREMIERE_UXP_PORT` to use another loopback port.
 
-When enabled, MCP discovery includes the original 19 UXP tools, 21 consolidated stable workflows, and eight third-wave tools. The first expansion covers effects, deterministic timeline selection, selection batches, scene detection, proxy/ingest, relink, metadata, color conformance, Source Monitor audition, storage, and least-privilege workspace access. The second adds Project-panel selection, marker CRUD, bin organization, sequence settings, imports, typed effect parameters/keyframes, track-item transforms, SequenceEditor timeline edits, sequence lifecycle, and AME encoding. The third wave begins with a redacted event journal, conservative AME terminal receipts, explicit host-readiness gates, safe multi-project sessions, lease-based growing-media control, namespaced workflow checkpoints, bounded media-health maintenance, caption-aware track mute state, and transactional source trim/framing documented in [the third-wave workflow matrix](docs/third-wave-uxp-workflows.md). A separate [hybrid benchmark gate](docs/uxp-hybrid-benchmark.md) keeps native acceleration disabled until reproducible cross-platform evidence exists. See also [the first stable workflow matrix](docs/uxp-stable-workflows.md) and [the next-ten workflow matrix](docs/uxp-next-ten-workflows.md). Commands are advertised only while the authenticated local UXP bridge is connected; the host capability handshake remains the authority for support in the running Premiere build. A failed UXP command is never silently retried through CEP because the first operation may have partially succeeded.
+When enabled, MCP discovery includes 54 capability-gated UXP additions. The first expansion covers effects, deterministic timeline selection, selection batches, scene detection, proxy/ingest, relink, metadata, color conformance, Source Monitor audition, storage, and least-privilege workspace access. The second adds Project-panel selection, marker CRUD, bin organization, sequence settings, imports, typed effect parameters/keyframes, track-item transforms, SequenceEditor timeline edits, sequence lifecycle, and AME encoding. The third wave begins with a redacted event journal, conservative AME terminal receipts, explicit host-readiness gates, safe multi-project sessions, lease-based growing-media control, namespaced workflow checkpoints, bounded media-health maintenance, caption-aware track mute state, and transactional source trim/framing documented in [the third-wave workflow matrix](docs/third-wave-uxp-workflows.md). The bounded migration surface also includes a non-ripple selected-item lift plus native video-transition listing and transactions; it does not claim direct empty-track create/delete or global redo support. A separate [hybrid benchmark gate](docs/uxp-hybrid-benchmark.md) keeps native acceleration disabled until reproducible cross-platform evidence exists. See also [the first stable workflow matrix](docs/uxp-stable-workflows.md) and [the next-ten workflow matrix](docs/uxp-next-ten-workflows.md). Commands are advertised only while the authenticated local UXP bridge is connected; the host capability handshake remains the authority for support in the running Premiere build. A failed UXP command is never silently retried through CEP because the first operation may have partially succeeded.
 
 The panel now requests access to one operator-selected workspace instead of declaring full filesystem access. Choose the folder in the panel before invoking a path-based UXP workflow. Media, relink, preset, export, and Source Monitor file paths must remain inside it; the persistent capability token and native root path are never returned over MCP. Lexical containment alone cannot exclude symlink, junction, or reparse-point escapes, and Adobe's request-scoped UXP filesystem API does not document canonical-path resolution. Builds without a host-supplied canonical resolver therefore advertise path-based UXP commands as unsupported and fail closed at invocation; use the existing CEP fallback for those operations.
 
@@ -508,11 +579,11 @@ The file-based IPC bridge is simple, reliable, and works across macOS and Window
 
 ---
 
-## Tools (288 core total; 286 under the default profile; 336 with a connected UXP bridge)
+## Tools (320 core total; 318 under the default profile; 372 with a connected UXP bridge)
 
 The [complete supported-actions catalog](docs/supported-actions.md) lists every
 registered core tool, the two tools restricted behind explicit `unsafe-script`
-authority, and all 50 authenticated UXP additions with their current action or mode
+authority, and all 54 authenticated UXP additions with their current action or mode
 values. It is generated from the same MCP registration surface returned to clients;
 the tables below are a shorter workflow-oriented overview.
 
@@ -556,8 +627,7 @@ the tables below are a shorter workflow-oriented overview.
 | `ripple_delete` | Remove clip and close gap (QE) |
 | `roll_edit` / `slide_edit` / `slip_edit` | Professional trim modes (QE) |
 | `move_clip_to_track` | Move between tracks (QE) |
-| `reverse_clip` | Reverse direction (QE, host-dependent) |
-| `speed_change` / `set_clip_speed_qe` | Unavailable: Premiere has no supported scripting API for changing clip speed |
+| `reverse_clip` / `speed_change` / `set_clip_speed_qe` | Unavailable: Premiere has no supported scripting API for changing a timeline clip's speed or direction |
 | `split_clip` / `trim_clip` / `move_clip` | Basic edits; trim verifies source points and visible timeline edges |
 | `set_clip_properties` | Opacity, scale, rotation, position (speed requests fail before mutation) |
 | `link_selection` / `unlink_selection` | Link/unlink A/V |
@@ -571,8 +641,8 @@ the tables below are a shorter workflow-oriented overview.
 > to blend adjacent source frames. See [issue #21](https://github.com/leancoderkavy/premiere-pro-mcp/issues/21).
 
 > **Speed, caption, and visual-keyframe boundaries:** Premiere Pro 26.3 exposes no supported
-> scripting setter or Time Remapping component for timeline-clip speed. `speed_change`,
-> `set_clip_speed_qe`, and `set_clip_properties` with `speed` now stop before host mutation;
+> scripting setter or Time Remapping component for timeline-clip speed or direction. `reverse_clip`,
+> `speed_change`, `set_clip_speed_qe`, and `set_clip_properties` with `speed` now stop before host mutation;
 > use the Speed/Duration UI or pre-render retimed media. `add_text_overlay` likewise stops
 > before mutation because a raw-text-to-caption API is not exposed; import an `.srt`/`.vtt`
 > and use `create_caption_track`, or use a MOGRT/PNG overlay. Keyframe and caption-track
@@ -673,7 +743,7 @@ than presenting UI-only operations as available tools.
 | `set_offline` / `has_proxy` / `detach_proxy` | Offline/proxy management |
 | `set_override_frame_rate` | Override FPS |
 | `set_scale_to_frame_size` | Auto-scale to sequence frame |
-| `get_xmp_metadata` / `set_xmp_metadata` | Raw XMP access |
+| `get_xmp_metadata` / `set_xmp_metadata` | Raw XMP access; writes merge a well-formed patch without removing unrelated fields |
 | `get_color_space` | Color space info |
 
 ### Sequence Management (11)
@@ -708,15 +778,29 @@ Track targeting, batch operations, markers, audio levels, motion/transform, meta
 
 ## MCP Resources
 
-The server exposes four LLM context resources and eleven workflow prompts:
+The server exposes fourteen LLM context resources and eleven workflow prompts:
 
 | Resource URI | Description |
 | :----------- | :---------- |
 | `config://premiere-instructions` | Best practices: workflow order, timeline rules, effect tips, error handling |
 | `config://extendscript-reference` | Complete ExtendScript API reference for writing custom scripts |
 | `config://premiere-workflows` | Machine-readable catalog for rough cuts, dialogue cleanup, captions, and delivery |
-
-These are automatically available to MCP clients that support resources, giving the AI deep context about how to drive Premiere Pro effectively.
+| `config://premiere-project-context` | Revisioned local project-context indexing and retrieval workflow |
+| `premiere://project/info` | Fresh, path-redacted current-project and active-sequence summary |
+| `premiere://project/sequences` | Bounded sequence inventory with stable Premiere IDs |
+| `premiere://project/media` | Bounded, path-redacted project-media inventory |
+| `premiere://project/bins` | Bounded, path-redacted project-bin inventory |
+| `premiere://timeline/active` | Bounded active-timeline tracks, clips, and markers snapshot |
+| `premiere://effects/available` | Bounded video/audio effect catalog for planning |
+| `premiere://effects/applied` | Bounded active-timeline component inventory |
+| `premiere://transitions/available` | Bounded video/audio transition catalog for planning |
+| `premiere://export/presets` | Bounded export-preset names and formats, without native paths |
+| `premiere://project/metadata` | Read-only project and active-timeline summary, without paths or timestamps |
+
+The ten `premiere://` snapshots are read-only CEP bridge requests. They include a
+revision token for stale-state detection and omit native media, project-tree, preset,
+and output paths. A successful snapshot proves bridge readback only—not licensed-host
+feature coverage, playback, rendering, or editorial correctness.
 
 ---
 
@@ -801,10 +885,18 @@ Then connect with:
 | `POSTHOG_DISTINCT_ID` | Optional stable anonymous server identifier | Fly machine ID or random boot ID |
 
 When PostHog is enabled, the server records `mcp_connection_attempt`,
-`mcp_request`, `mcp_request_rejected`, and `mcp_tool_call`. Events contain operational fields such as
-method, tool name, outcome, status code, and duration. Authentication tokens,
-IP addresses, MCP arguments, project paths, media names, and tool results are
-never sent. Person profiles are disabled for these events.
+`mcp_request`, `mcp_request_rejected`, and `mcp_tool_call`. It also records
+`premiere_mcp_activation_completed` only after the read-only
+`verify_premiere_connection` check confirms the selected bridge, an open
+project, and an active sequence. Events contain bounded operational fields such
+as method, tool name, outcome, status code, duration, and selected bridge.
+Authentication tokens, IP addresses, MCP arguments, project paths, media names,
+and tool results are never sent. Person profiles are disabled for these events.
+
+This signal is an aggregate emission, not proof that an analytics provider
+received it, a count of unique people or editors, or evidence that an editing
+workflow succeeded. It does not carry a person or editor identifier, so it
+cannot safely infer "first value."
 
 ---
 
@@ -815,7 +907,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 288 tools, filtered by authority profile
+│   ├── server.ts                # MCP server — registers 320 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.13.0" ExtensionBundleName="MCP for Adobe Premiere Pro">
+<ExtensionManifest Version="7.0" ExtensionBundleId="com.mcp.premiere.bridge" ExtensionBundleVersion="1.14.2" ExtensionBundleName="MCP for Adobe Premiere Pro">
   <ExtensionList>
-    <Extension Id="com.mcp.premiere.bridge.panel" Version="1.13.0"/>
-    <Extension Id="com.mcp.premiere.bridge.headless" Version="1.13.0"/>
+    <Extension Id="com.mcp.premiere.bridge.panel" Version="1.14.2"/>
+    <Extension Id="com.mcp.premiere.bridge.headless" Version="1.14.2"/>
   </ExtensionList>
   <ExecutionEnvironment>
     <HostList>

package/cep-plugin/index.html

@@ -81,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.13.0</strong>
+        <strong id="updateTitle">Version 1.14.2</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

@@ -8,6 +8,8 @@ var pollInterval = null;
 var commandCount = 0;
 var tempDir = "";
 var POLL_MS = 200;
+var HEARTBEAT_MS = 1000;
+var heartbeatInterval = null;
 
 // ---- Logging ----
 function log(msg, cls) {
@@ -136,12 +138,57 @@ function writeFile(filePath, content) {
   }
 }
 
+// Publish responses atomically so the MCP process never sees a partially-written
+// JSON file. The staging suffix is not a response filename the server will read.
+function writeResponseFile(filePath, content) {
+  var stagedPath = filePath + ".staged";
+  try {
+    fs.writeFileSync(stagedPath, content, "utf-8");
+    fs.renameSync(stagedPath, filePath);
+    return true;
+  } catch (e) {
+    deleteFile(stagedPath);
+    log("Error publishing " + filePath + ": " + e.message, "err");
+    return false;
+  }
+}
+
 function deleteFile(filePath) {
   try {
     if (fs.existsSync(filePath)) fs.unlinkSync(filePath);
   } catch (e) {}
 }
 
+// The heartbeat carries only protocol state. It is published by rename so a
+// server never observes partial JSON, and an older server can ignore it.
+function writeBridgeHeartbeat() {
+  if (!tempDir) return;
+  var heartbeatPath = path.join(tempDir, "bridge-heartbeat.json");
+  var stagedPath = heartbeatPath + "." + ENGINE_ID + ".staged";
+  try {
+    fs.writeFileSync(stagedPath, JSON.stringify({
+      protocolVersion: 1,
+      state: bridgeRunning ? "running" : "waiting"
+    }), "utf-8");
+    fs.renameSync(stagedPath, heartbeatPath);
+  } catch (e) {
+    deleteFile(stagedPath);
+  }
+}
+
+function startBridgeHeartbeat() {
+  if (heartbeatInterval) clearInterval(heartbeatInterval);
+  writeBridgeHeartbeat();
+  heartbeatInterval = setInterval(writeBridgeHeartbeat, HEARTBEAT_MS);
+}
+
+function stopBridgeHeartbeat() {
+  if (heartbeatInterval) clearInterval(heartbeatInterval);
+  heartbeatInterval = null;
+  // Keep the last heartbeat in place. Its age lets newer servers diagnose a
+  // stopped connector, while concurrent visible/headless panels stay isolated.
+}
+
 // ---- Script Execution ----
 function executeScript(script, callback) {
   // Script is already wrapped in an IIFE by the MCP server's buildScript(),
@@ -234,7 +281,7 @@ function processOneCommand(cmdFileName) {
       }
     }
 
-    writeFile(resFilePath, response);
+    writeResponseFile(resFilePath, response);
   });
 }
 
@@ -249,6 +296,7 @@ function startBridge() {
 
   ensureDir(tempDir);
   bridgeRunning = true;
+  startBridgeHeartbeat();
   setStatus("waiting", "Connector running");
   log("Connector started and ready for safe checks.", "ok");
 
@@ -264,6 +312,8 @@ function startBridge() {
 
 function stopBridge() {
   bridgeRunning = false;
+  writeBridgeHeartbeat();
+  stopBridgeHeartbeat();
   if (pollInterval) clearInterval(pollInterval);
   pollInterval = null;
 
@@ -423,6 +473,7 @@ function handleUpdateClick() {
   // one to click Start, and macOS periodically purges the temp dir — so create it
   // rather than gating auto-start on its existence.
   ensureDir(tempDir);
+  startBridgeHeartbeat();
   log("Auto-starting bridge...");
   setTimeout(startBridge, 500);
   setTimeout(checkForUpdates, 1200);

package/cep-plugin/updater.cjs

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

package/dist/bridge/file-bridge.d.ts

@@ -1,18 +1,39 @@
+export declare const BRIDGE_HEARTBEAT_FILE = "bridge-heartbeat.json";
+export declare const BRIDGE_HEARTBEAT_STALE_MS = 3000;
 export interface BridgeOptions {
     tempDir?: string;
     timeoutMs?: number;
+    /**
+     * Reject a health-style command without publishing it when a current CEP
+     * connector explicitly reports that it is waiting or its heartbeat is stale.
+     * A missing heartbeat remains compatible with older installed connectors.
+     */
+    failFastOnUnreadyHeartbeat?: boolean;
 }
 export interface CommandResult {
     success: boolean;
     data?: unknown;
     error?: string;
 }
+export type BridgeLivenessState = "running" | "waiting" | "stale" | "unknown";
+export interface BridgeLiveness {
+    state: BridgeLivenessState;
+    ageMs: number | null;
+}
 export declare function getTempDir(options?: BridgeOptions): string;
+/**
+ * Inspect the CEP panel's small, content-free heartbeat. This never creates a
+ * directory or reads command, response, project, or media data. Unknown is
+ * intentionally non-fatal so a server upgrade stays compatible with older CEP
+ * panels that do not publish a heartbeat yet.
+ */
+export declare function getBridgeLiveness(options?: BridgeOptions, nowMs?: number): BridgeLiveness;
 /**
  * Send a command (ExtendScript) to the CEP plugin and wait for a response.
  *
  * Protocol:
- * 1. Write script to <tempDir>/cmd_<id>.jsx
+ * 1. Write the script to a staging file, then atomically publish it as
+ *    <tempDir>/cmd_<id>.jsx. The CEP panel only sees complete commands.
  * 2. CEP plugin picks it up, executes, writes result to <tempDir>/res_<id>.json
  * 3. We poll for the response file and parse it.
  */