creative-pipeline-mcp 0.2.14-alpha.0

package/LICENSE

@@ -0,0 +1,18 @@
+Apache License
+Version 2.0, January 2004
+https://www.apache.org/licenses/
+
+Copyright 2026 Creative Pipeline MCP contributors
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at:
+
+https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+

package/NOTICE

@@ -0,0 +1,9 @@
+Creative Pipeline MCP
+Copyright 2026 Creative Pipeline MCP contributors
+
+This repository is an unofficial integration scaffold and QC pipeline.
+It is not affiliated with Blender, Adobe, Premiere Pro, or 3D-Agent.
+
+Optional external tools referenced by adapter manifests keep their own licenses.
+See docs/LICENSING.md and third_party_licenses/README.md.
+

package/README.md

@@ -0,0 +1,205 @@
+# Creative Pipeline MCP
+
+[![CI](https://github.com/taiyuhiga/creative-pipeline-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/taiyuhiga/creative-pipeline-mcp/actions/workflows/ci.yml)
+
+QC-first MCP pipeline for Blender asset workflows and Adobe Premiere media workflows.
+
+This repository implements a split creative pipeline architecture:
+
+- `creative-mcp-core`: tool registry, router, approval policy, artifact store, QC reports, license manifest
+- `blender-pro-mcp`: Blender/glTF asset inspection, preview artifacts, validation, optimization/export fallbacks
+- `premiere-pro-mcp`: media ingest, ffprobe indexing, delivery QC, rough-cut OTIO plans, captions, audio/export plans
+- `blender-gpl-adapters`: optional GPL adapter manifests kept separate from the core packages
+- `premiere-windows-adapter`: Windows CEP/WebSocket reference guardrails
+- `premiere-cep-panel`: minimal CEP panel scaffold for consuming Premiere IPC commands
+- `director-agent`: production planning, Blender to Premiere handoff, full production reports, multi-agent review
+- `dashboard`: local artifact/QC report viewer
+
+## Status
+
+Current version: `0.2.14-alpha.0`
+
+This is an alpha. The QC-first path runs without Blender or Premiere installed:
+
+- GLB/glTF metadata inspection and asset QC
+- Media metadata QC through `ffprobe` when FFmpeg is installed
+- Artifact writing, logs, license manifest, and approval policy
+- server-side JSON Schema validation
+- workspace input allowlists for local file reads
+- pending approval artifacts for elevated tools
+- real CLI adapters when optional tools are installed: headless Blender preview, bundled `gltf-transform`, optional `gltfpack`, FFmpeg black/silence/loudness checks, thumbnail extraction, FFmpeg `libvmaf` scoring
+- Blender bridge queue/status IPC and a headless worker for trusted external scene and asset adapters
+- Blender asset QC for triangle budget, origin, scale, normals, primary UVs, material count, and texture slots
+- Blender optimization size comparison metrics and safe generated Blender script artifacts for game asset jobs
+- template-based basic Blender repair for GLB/glTF assets when Blender is installed
+- optional WhisperX, PySceneDetect, pyloudnorm, and VMAF adapter tools
+- Dashboard approval queue UI, artifact previews, and job history
+- Premiere CEP bridge for OTIO media import, duplicate import avoidance, sequence creation attempts, timeline-positioned clip insertion attempts, export command queueing, brand package command queueing, and standardized status JSON
+- Premiere project-specific delivery builder for timeline, brand package, export plan, and CEP queue generation
+- Premiere CEP host simulator for queue/status validation without a live Premiere runtime
+- Premiere CEP unsigned package generation and optional ZXP signing hook
+- approval-to-rerun flow in the dashboard for approved elevated tool requests
+- Premiere CEP status reader
+- Blender and generated-MP4 Premiere e2e examples
+- v2.0+ manifests for USD, MaterialX, engine profiles, brand packages, social variants, subtitles, thumbnails, and Director Agent handoff
+- MCP-style stdio JSON-RPC methods: `initialize`, `tools/list`, `tools/call`, `ping`
+- CI runs unit tests on Node.js 20, 22, and 24, with separate package, adapter, Blender e2e, and Premiere QC e2e jobs
+- guarded npm trusted-publishing workflow for release tags when npmjs.com trusted publisher settings are configured
+
+Premiere timeline mutation and export/brand-package requests are queued through a trusted CEP file-based IPC adapter, with a minimal CEP panel scaffold included. WhisperX, PySceneDetect, pyloudnorm, VMAF, and GPL tools remain optional external adapters.
+
+## Capability Status
+
+| Feature | Status |
+| --- | --- |
+| GLB/glTF metadata QC | Working |
+| Headless Blender preview | Working when Blender is installed |
+| Blender bridge queue/status | Alpha worker process |
+| glTF optimization | Working with `gltf-transform`; optional `gltfpack` |
+| Basic Blender repair | Working when Blender is installed |
+| Premiere media QC | Working when FFmpeg is installed |
+| Premiere VMAF scoring | Working when FFmpeg includes `libvmaf` |
+| Adapter availability report | Working with text and JSON output |
+| Dashboard approvals/previews | Localhost-only, token-protected alpha |
+| Premiere timeline creation | Project delivery builder + CEP scaffold |
+| Premiere final export | Project export plan + CEP queue command |
+| Full professional editing | Not v1 complete |
+
+## Install
+
+```bash
+npm install
+npm run build
+npm test
+npm run check:adapters
+npm run check:adapters -- --json
+```
+
+Blender e2e sample:
+
+```bash
+npm run build
+node examples/blender-e2e.mjs
+```
+
+Blender bridge queue sample:
+
+```bash
+npm run build
+node examples/blender-bridge-queue.mjs
+```
+
+Blender bridge worker dry-run:
+
+```bash
+npm run blender:bridge-worker -- --once --dry-run
+```
+
+Premiere media QC / CEP queue sample:
+
+```bash
+npm run build
+node examples/premiere-qc-e2e.mjs
+node examples/premiere-project-delivery.mjs
+npm run simulate:premiere-cep -- --queue artifacts/examples/premiere-project-delivery/cep_queue --status artifacts/examples/premiere-project-delivery/cep_status
+```
+
+Typical artifacts:
+
+```text
+artifacts/
+  adapter_check_report.json
+  blender/
+    cube_preview.png
+    cube_asset_qc_report.json
+    cube_optimized.glb
+  premiere/
+    source_rough_cut.otio
+    source_delivery_qc_report.json
+    source_thumbnail_1.png
+    cep_queue/
+```
+
+## Run MCP Servers
+
+```bash
+npm run start:core
+npm run start:blender
+npm run start:premiere
+```
+
+Dashboard:
+
+```bash
+CREATIVE_MCP_DASHBOARD_TOKEN=change-me npm run start:dashboard
+open "http://127.0.0.1:4173/?token=change-me"
+```
+
+Premiere CEP panel scaffold:
+
+```bash
+npm run install:premiere-cep
+npm run package:premiere-cep -- --verify
+```
+
+Release assets:
+
+```bash
+npm run release:assets
+```
+
+npm publishing:
+
+```bash
+npm publish --dry-run --provenance
+```
+
+For GitHub Actions publishing, configure npm trusted publishing for `.github/workflows/npm-publish.yml`, then set `NPM_TRUSTED_PUBLISHING_ENABLED=true` in repository variables.
+
+Detailed docs:
+
+- `docs/INSTALL_DASHBOARD.md`
+- `docs/PREMIERE_E2E_TEST.md`
+- `docs/API_TOOLS.md`
+- `docs/COMPATIBILITY_MATRIX.md`
+- `docs/CEP_STATUS_SCHEMA.md`
+- `docs/ARTIFACT_SCHEMA.md`
+- `docs/RELEASE_PROCESS.md`
+- `docs/TROUBLESHOOTING.md`
+
+Example `tools/list` request:
+
+```json
+{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}
+```
+
+Example Blender QC call:
+
+```json
+{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"blender.validate_asset","arguments":{"path":"examples/minimal.glb","maxTriangles":50000}}}
+```
+
+Example Premiere QC call:
+
+```json
+{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"premiere.run_delivery_qc","arguments":{"path":"source.mp4","targetWidth":1080,"targetHeight":1920,"maxDuration":60}}}
+```
+
+Artifacts are written to `artifacts/` unless `CREATIVE_MCP_ARTIFACTS` is set.
+Input files must be under `CREATIVE_MCP_WORKSPACE_ROOTS`; by default that is the current working directory.
+
+## Safety
+
+Default permission is `safe_write`. Tools marked `project_write`, `destructive`, or `admin` write a pending approval artifact unless a higher permission level is configured:
+
+```bash
+CREATIVE_MCP_PERMISSION=project_write npm run start:premiere
+```
+
+Use copies for production projects. Direct destructive operations, raw `bpy`, raw ExtendScript, deletion, publishing, external upload, cloud sync, and GPL adapter activation are not enabled by default.
+
+## Licensing And Trademarks
+
+This is an unofficial tool. It is not affiliated with or endorsed by Blender, Adobe, Premiere Pro, or 3D-Agent. Blender, Adobe, and Premiere Pro trademarks belong to their owners.
+
+3D-Agent is not included. GPL tools are separated into optional external adapters so the Apache-2.0 core packages do not directly import GPL code.

package/SECURITY.md

@@ -0,0 +1,19 @@
+# Security Policy
+
+## Supported Branch
+
+Security fixes target `main`.
+
+## Model
+
+The default runtime permission is `safe_write`. Destructive actions, raw script execution, final delivery export, publishing, external upload, cloud sync, shell operations, and GPL adapter activation require explicit elevated configuration or external approval.
+
+Do not connect these servers to untrusted MCP clients. Premiere and Blender bridge adapters can control local creative applications once enabled.
+
+Input paths are restricted to `CREATIVE_MCP_WORKSPACE_ROOTS`. Symlinks that resolve outside those roots are rejected by default; set `CREATIVE_MCP_ALLOW_SYMLINKS=true` only for trusted workspaces.
+
+The dashboard binds to `127.0.0.1` and requires `CREATIVE_MCP_DASHBOARD_TOKEN`. Do not expose it through a proxy or public interface.
+
+## Reporting
+
+Open a private security advisory or contact the repository owner. Do not include private media, project files, credentials, or unpublished client work in public reports.

package/docs/API_TOOLS.md

@@ -0,0 +1,74 @@
+# API Tools
+
+The public alpha tool schemas are intentionally strict. Unknown top-level input properties are rejected before execution.
+
+## Core
+
+- `core.list_capabilities`
+- `core.read_license_manifest`
+- `core.write_run_log`
+
+## Blender
+
+- `blender.read_bridge_status`
+- `blender.await_bridge_status`
+- `blender.create_scene`
+- `blender.apply_material`
+- `blender.modify_asset`
+- `blender.create_asset`
+- `blender.inspect_scene`
+- `blender.configure_engine_profile`
+- `blender.create_usd_pipeline`
+- `blender.create_materialx_workflow`
+- `blender.plan_rig_animation`
+- `blender.validate_asset`
+- `blender.render_preview`
+- `blender.optimize_asset`
+- `blender.export_game_ready`
+- `blender.create_game_asset`
+- `blender.create_material_pack`
+- `blender.fix_asset_issues`
+- `blender.repair_basic_asset`
+
+## Premiere
+
+- `premiere.read_cep_status`
+- `premiere.await_cep_status`
+- `premiere.transcribe_media`
+- `premiere.detect_scenes`
+- `premiere.measure_loudness`
+- `premiere.measure_vmaf`
+- `premiere.build_timeline_from_otio`
+- `premiere.ingest_media`
+- `premiere.index_media`
+- `premiere.run_delivery_qc`
+- `premiere.make_rough_cut`
+- `premiere.build_project_delivery`
+- `premiere.auto_caption`
+- `premiere.mix_audio`
+- `premiere.export_video`
+- `premiere.finalize_export_qc`
+- `premiere.export_social_variants`
+- `premiere.apply_brand_package`
+- `premiere.create_multilanguage_subtitles`
+- `premiere.generate_thumbnail_plan`
+- `premiere.repurpose_podcast`
+- `premiere.fix_qc_issues`
+
+## Director
+
+- `director.plan_production`
+- `director.handoff_blender_asset`
+- `director.full_production_report`
+- `director.multi_agent_review`
+
+## Stability
+
+Alpha schemas may still change. The intended v1 freeze covers:
+
+- tool names
+- required fields
+- output `structuredContent`
+- QC report schema
+- CEP status schema
+- artifact layout

package/docs/ARCHITECTURE.md

@@ -0,0 +1,28 @@
+# Architecture
+
+Creative Pipeline MCP is split into small packages:
+
+- `core`: registry, router, job queue, approval policy, artifact store, QC report schema, license manifest
+- `blender-pro-mcp`: glTF/GLB inspection, asset QC, preview/export/optimization artifact flow
+- `premiere-pro-mcp`: media ingest, metadata indexing, rough cut plans, captions, audio/export plans, delivery QC
+- `premiere-cep-panel`: minimal CEP panel scaffold for file-based Premiere IPC commands
+- `blender-gpl-adapters`: optional GPL process-boundary manifests
+- `premiere-windows-adapter`: CEP/WebSocket reference checks for Windows
+- `dashboard`: artifact, QC report, and approval queue viewer
+
+The dashboard reads `artifacts/approvals/pending`, resolves approve/reject decisions into `artifacts/approvals/resolved`, and reruns approved elevated tool requests with the approved risk level.
+
+The public tool surface stays small. Low-level OSS integrations are adapter capabilities selected behind macro tools.
+
+## MCP Methods
+
+The servers implement a stdio JSON-RPC subset:
+
+- `initialize`
+- `ping`
+- `tools/list`
+- `tools/call`
+
+## Artifact Flow
+
+All generated reports, previews, manifests, logs, captions, and OTIO plans are written under `artifacts/` by default.

package/docs/ARTIFACT_SCHEMA.md

@@ -0,0 +1,43 @@
+# Artifact Schema
+
+Artifacts are written under `CREATIVE_MCP_ARTIFACTS`, defaulting to `artifacts/`.
+
+## Common Layout
+
+```text
+artifacts/
+  adapter_check_report.json
+  approvals/
+    pending/
+    resolved/
+  blender/
+  examples/
+  logs/
+  premiere/
+    cep_queue/
+    cep_status/
+```
+
+## Approval Request
+
+```json
+{
+  "action": "blender.export_game_ready",
+  "risk": "project_write",
+  "currentPermission": "safe_write",
+  "requestedAt": "2026-01-01T00:00:00.000Z",
+  "expiresAt": "2026-01-02T00:00:00.000Z",
+  "approvalToken": "00000000-0000-4000-8000-000000000000",
+  "artifactRoot": "/workspace/artifacts",
+  "workspaceRoots": ["/workspace"],
+  "expectedOutputs": {
+    "artifacts": "tool-dependent",
+    "sideEffects": "project_write"
+  },
+  "input": {}
+}
+```
+
+## Adapter Check Report
+
+See `docs/examples/adapter_check_report.sample.json`.

package/docs/BLENDER_BRIDGE_STATUS_SCHEMA.md

@@ -0,0 +1,42 @@
+# Blender Bridge Status Schema
+
+Trusted Blender bridge adapters can write status files under `artifacts/blender/bridge_status` or `CREATIVE_MCP_BLENDER_STATUS_DIR`.
+
+```json
+{
+  "schema": "creative.pipeline.blender.status.v1",
+  "commandId": "1780000000000-abc",
+  "commandType": "create_asset",
+  "status": "success",
+  "message": "asset created",
+  "details": {
+    "outputPath": "artifacts/blender/asset.glb",
+    "previewPath": "artifacts/blender/asset_preview.png"
+  },
+  "finishedAt": "2026-01-01T00:00:00.000Z"
+}
+```
+
+Supported `commandType` values:
+
+- `create_scene`
+- `create_asset`
+- `modify_asset`
+- `apply_material`
+- `run_safe_script`
+
+Supported `status` values:
+
+- `success`
+- `accepted`
+- `error`
+
+`blender.read_bridge_status` reads normalized status records. `blender.await_bridge_status` polls by `commandId` and/or `commandType`.
+
+The bundled worker can consume queued commands and write this schema:
+
+```bash
+npm run blender:bridge-worker -- --once --dry-run
+```
+
+When not in dry-run mode, set `BLENDER_BIN` or make `blender` available on `PATH`. Processed command files are archived under `bridge_queue/processed` by default.

package/docs/CEP_STATUS_SCHEMA.md

@@ -0,0 +1,35 @@
+# CEP Status Schema
+
+Premiere CEP status files use:
+
+```json
+{
+  "schema": "creative.pipeline.premiere.status.v1",
+  "commandId": "1780000000000-abc",
+  "commandType": "build_timeline_from_otio",
+  "status": "success",
+  "message": "timeline build completed",
+  "details": {
+    "imported": 1,
+    "media": 1,
+    "inserted": 1,
+    "sequenceName": "Creative Pipeline Rough Cut"
+  },
+  "finishedAt": "2026-01-01T00:00:00.000Z",
+  "processedAt": "2026-01-01T00:00:01.000Z"
+}
+```
+
+Supported `commandType` values:
+
+- `build_timeline_from_otio`
+- `export_sequence`
+- `apply_brand_package`
+
+Supported `status` values:
+
+- `success`
+- `accepted`
+- `error`
+
+The MCP status reader normalizes legacy status files to this schema. `premiere.await_cep_status` can poll by `commandId` and/or `commandType`, and `premiere.finalize_export_qc` uses `export_sequence` status details to locate the exported file before writing delivery QC.

package/docs/COMPATIBILITY_MATRIX.md

@@ -0,0 +1,36 @@
+# Compatibility Matrix
+
+This matrix tracks what must be verified before v1.
+
+| Area | Status | Evidence |
+| --- | --- | --- |
+| Node 20 | CI covered | `unit-test (20)` |
+| Node 22 | CI covered | `unit-test (22)` |
+| Node 24 | CI covered | `unit-test (24)` |
+| npm pack | CI covered | `package-test` |
+| FFmpeg installed | CI covered | `premiere-qc-e2e` installs FFmpeg |
+| FFmpeg missing | Partial | adapter check reports missing tools without failing |
+| FFmpeg libvmaf installed/missing | Adapter check | `ffmpeg-libvmaf` availability report |
+| Blender installed | Local/optional CI | `blender-e2e-optional` runs when available |
+| Blender missing | Partial | renderer/optimizer fallbacks are tested through unit paths |
+| macOS + Blender | Local covered | local e2e evidence |
+| macOS + Premiere | Manual required | see `docs/PREMIERE_E2E_TEST.md` |
+| Windows + Blender | Manual required | no current hosted verification |
+| Windows + Premiere | Manual required | no current hosted verification |
+| WhisperX installed/missing | Adapter check | availability report |
+| PySceneDetect installed/missing | Adapter check | availability report |
+| pyloudnorm installed/missing | Adapter check | availability report |
+
+Manual results should be recorded with:
+
+```text
+OS:
+Node:
+Blender:
+Premiere:
+FFmpeg:
+Command:
+Result:
+Artifacts:
+Notes:
+```

package/docs/GPL_ADAPTERS.md

@@ -0,0 +1,19 @@
+# GPL Adapters
+
+The GPL adapter package is separate by design.
+
+Use process boundaries:
+
+- command-line calls
+- sockets
+- temporary JSON files
+- Blender addon execution outside the Apache-2.0 core
+
+Optional adapter targets:
+
+- BlenderProc
+- BlenderGIS
+- Sverchok
+
+Do not directly import GPL implementation code into `packages/core`, `packages/blender-pro-mcp`, or `packages/premiere-pro-mcp`.
+

package/docs/INSTALL_BLENDER.md

@@ -0,0 +1,39 @@
+# Blender Install Notes
+
+The alpha QC path does not require Blender for `.glb` and `.gltf` inspection.
+
+For rendered previews, set `BLENDER_BIN` or make `blender` available on `PATH`. `blender.render_preview` will use headless Blender when available and falls back to a placeholder preview when it is not.
+
+For `.blend` inspection, procedural generation, or scene mutation, install Blender separately and connect a trusted external bridge adapter. `blender.create_scene`, `blender.create_asset`, `blender.modify_asset`, `blender.apply_material`, and `blender.create_game_asset` queue bridge commands under `CREATIVE_MCP_BLENDER_IPC_DIR` for that adapter to consume. Keep raw `bpy` execution disabled unless the client and project are trusted.
+
+Default bridge paths:
+
+```text
+artifacts/blender/bridge_queue
+artifacts/blender/bridge_status
+```
+
+Use `blender.read_bridge_status` or `blender.await_bridge_status` to read status JSON written by the bridge adapter. For status records, see `docs/BLENDER_BRIDGE_STATUS_SCHEMA.md`.
+
+Generated bridge queue sample:
+
+```bash
+npm run build
+node examples/blender-bridge-queue.mjs
+```
+
+Worker process:
+
+```bash
+npm run blender:bridge-worker -- --once --dry-run
+BLENDER_BIN=/Applications/Blender.app/Contents/MacOS/Blender npm run blender:bridge-worker -- --once
+```
+
+The worker drains command JSON from the queue, writes normalized status JSON, archives processed commands under `bridge_queue/processed`, and runs generated safe Blender scripts through `BLENDER_BIN` when not in dry-run mode. Use `--queue`, `--status`, `--output`, `--archive`, `--poll-ms`, and `--max-commands` to point it at project-specific paths. Without `--once`, it keeps polling.
+
+Suggested external adapter roles:
+
+- glTF-Transform or gltfpack optimization through `GLTF_TRANSFORM_BIN`, `GLTFPACK_BIN`, or `PATH`
+- meshoptimizer and xatlas
+- OpenImageIO/OpenColorIO preview and color checks
+- optional GPL adapters for BlenderProc, BlenderGIS, and Sverchok

package/docs/INSTALL_DASHBOARD.md

@@ -0,0 +1,47 @@
+# Dashboard
+
+The dashboard is a local-only artifact, preview, job-history, and approval viewer. It can approve elevated tool requests and rerun the approved tool, so it must not be exposed to a network.
+
+## Start
+
+```bash
+CREATIVE_MCP_DASHBOARD_TOKEN=change-me npm run start:dashboard
+```
+
+Open:
+
+```text
+http://127.0.0.1:4173/?token=change-me
+```
+
+The server binds to `127.0.0.1` only. `CREATIVE_MCP_DASHBOARD_TOKEN` is required. API requests must send the token as `x-creative-mcp-dashboard-token` or as the `token` query parameter.
+
+## APIs
+
+- `GET /api/reports`
+- `GET /api/artifacts`
+- `GET /api/artifacts/file?path=<artifact-relative-path>`
+- `GET /api/jobs`
+- `GET /api/approvals`
+- `POST /api/approvals/resolve`
+
+## Approval Risk
+
+Approving a pending request can rerun a `project_write`, `destructive`, or `admin` tool with the stored input. Review the request JSON before approving.
+
+Reject requests that:
+
+- reference unexpected source paths
+- request broad workspace access
+- target production project files directly
+- request raw script, shell, publishing, upload, or sync behavior
+
+## Environment
+
+```text
+PORT=4173
+CREATIVE_MCP_ARTIFACTS=artifacts
+CREATIVE_MCP_DASHBOARD_TOKEN=change-me
+```
+
+Do not proxy this dashboard or bind it to public interfaces.