# Windows Creative Tools Ports > Case study: maintained Windows 11 ports of Sam Wasserman’s open-source creative tools - **Type:** MCP server - **Install:** `agentstack add mcp-gumbiidigital-windows-creative-tools-ports` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [GumbiiDigital](https://agentstack.voostack.com/s/gumbiidigital) - **Installs:** 0 - **Category:** [Integrations](https://agentstack.voostack.com/c/integrations) - **Latest version:** 0.1.0 - **License:** Apache-2.0 - **Upstream author:** [GumbiiDigital](https://github.com/GumbiiDigital) - **Source:** https://github.com/GumbiiDigital/windows-creative-tools-ports - **Website:** https://github.com/GumbiiDigital/windows-creative-tools-ports ## Install ```sh agentstack add mcp-gumbiidigital-windows-creative-tools-ports ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Windows Creative Tools Ports An evidence-led engineering record for the maintained Windows 11 community editions of three open-source filmmaking tools originally created by **Sam Wasserman / Wasserman Productions**. > Originally created by Sam Wasserman / Wasserman Productions. Windows port and community Windows releases maintained by Gumbii Digital. This repository documents the requirements, implementation decisions, native builds, exact-artifact tests, security controls, defects, and upstream publication work. It does not replace the application forks, duplicate their source, or imply endorsement by Wasserman Productions. ## Shipped applications | Application | Definitive Windows prerelease | Maintained source | Accepted Windows contribution | |---|---|---|---| | Blockout | [v5.0.0-windows.2](https://github.com/GumbiiDigital/blockout/releases/tag/v5.0.0-windows.2) | [GumbiiDigital/blockout](https://github.com/GumbiiDigital/blockout) | [upstream PR #2](https://github.com/wassermanproductions/blockout/pull/2) | | Motion Previs Studio | [v4.1.0-windows.1](https://github.com/GumbiiDigital/motion-previs-studio/releases/tag/v4.1.0-windows.1) | [GumbiiDigital/motion-previs-studio](https://github.com/GumbiiDigital/motion-previs-studio) | [upstream PR #1](https://github.com/wassermanproductions/motion-previs-studio/pull/1) | | Stem Studio | [v1.1.0-windows.2](https://github.com/GumbiiDigital/stem-studio/releases/tag/v1.1.0-windows.2) | [GumbiiDigital/stem-studio](https://github.com/GumbiiDigital/stem-studio) | [upstream PR #2](https://github.com/wassermanproductions/stem-studio/pull/2) | The installers are unsigned, assisted, per-user NSIS prereleases for Windows 11 x64. Every release includes a SHA-256 ledger, open-source notices, modification record, asset/model manifest, SPDX and CycloneDX SBOMs, provenance, and FFmpeg corresponding-source material. ## Engineering record - [Implementation record](docs/IMPLEMENTATION-RECORD.md) — original intent, branch model, frozen baselines, dependency order, per-app changes, native packaging, and open-source boundaries. - [Verification and security](docs/VERIFICATION-AND-SECURITY.md) — proof ladder, physical-Windows versus clean-VM scope, screenshots and recordings, privacy controls, supply-chain checks, defect handling, and remaining risks. - [Thirty-six-scenario matrix](docs/36-SCENARIO-MATRIX.md) — twelve documented user scenarios per app, evidence tier, outcome, and measurable acceptance result. - [Operator handbook library](handbooks/README.md) — four complete Markdown and tagged-PDF editions for Blockout, Motion Previs Studio, Stem Studio, and the combined workflow. - [Upstream contributions](docs/UPSTREAM-CONTRIBUTIONS.md) — accepted Windows-port contributions, handbook disposition, and focused troubleshooting follow-ups. - [Release evidence summary](docs/QA-EVIDENCE.md) — exact installer hashes, native CI runs, and application-specific release gates. - [Publication SHA-256 manifest](docs/PUBLICATION-MANIFEST.sha256) — integrity ledger for this documentation revision. - [Publication policy](publication-policy.json) — machine-readable privacy checks, publication roots, and permanent PDF compatibility paths. ## Verification approach The work followed a traceable loop: ```text written requirement -> frozen source baseline -> isolated implementation branch -> automated source and package gates -> native Windows build after fresh dependency installation -> exact installer hash verification -> physical Windows workflow execution and capture -> defect record and targeted correction -> authoritative rerun -> privacy, licensing, link, PDF, and Git publication audit ``` A launch screen, a progress indicator, a generated file, or a verbal claim was never treated as sufficient proof on its own. Visual claims required visible application evidence; file claims required hashes and structural probes; cancellation claims required process-tree and partial-file checks; release claims required the exact hosted installer rather than a development build. The deeper application workflows and all 36 documentation-led scenarios were exercised on a physical Windows 11 x64 laptop. A separate clean Windows 11 VM was used for the clean-machine lifecycle gate: installer identity, Defender, selected-directory per-user installation, shortcuts, launch, process closure, uninstall, and retained user data. Those two evidence classes are intentionally not conflated. ## What was implemented - Electron 43 desktop foundations and assisted per-user NSIS installers with distinct community app IDs, uninstall identities, and data roots. - Cross-platform filesystem rules for drive letters, UNC paths, traversal prevention, junction containment, Unicode, apostrophes, spaces, and OneDrive-style nesting. - Windows process-tree cancellation and cleanup for Electron, FFmpeg, yt-dlp, uv, Python, and model workers. - Audited, packaged FFmpeg/FFprobe binaries with explicit resolution, provenance, licenses, checksums, and corresponding source. - Pinned MediaPipe, yt-dlp, Depth Anything, uv, CPython, and TIGER-DnR assets with integrity verification. - Packaged MCP bridges, versioned control descriptors, and the health-checked Motion Previs → Blockout handoff. - Native Windows CI, exact-artifact testing, checksums, SBOMs, provenance, attestations, and preservation of upstream licenses and credits. ## Architecture ```mermaid flowchart LR User["Windows 11 filmmaker"] --> B["Blockoutscene and camera blocking"] User --> M["Motion Previs Studiopose, depth, and control layers"] User --> S["Stem Studiodialogue, music, and SFX"] M -->|"versioned, health-checked handoff"| B Client["MCP client"] --> BM["Packaged Blockout MCP bridge"] --> B Client --> MM["Packaged Motion MCP bridge"] --> M Client --> SM["Packaged Stem MCP bridge"] --> S B --> F["Packaged FFmpeg/FFprobe"] M --> F S --> F S --> R["Private uv + CPython 3.12.10 + TIGER runtime"] ``` ```mermaid flowchart TD U["upstream mainoriginal application"] --> G["feature/windows-portgeneric reusable support"] G --> P["upstream pull request"] G --> D["release/gumbii-windowsisolated community identity"] D --> W["native Windows buildafter fresh npm ci"] W --> Q["source, package, runtime, physical-host, and clean-VM gates"] Q --> A["unsigned NSIS prerelease"] A --> C["checksums, SBOMs, provenance, notices, and source"] ``` ## Handbook publication The [operator handbook library](handbooks/README.md) contains four complete publications: | Handbook | Source edition | Reader edition | |---|---|---| | Blockout Operator Handbook | [Markdown](handbooks/blockout-sop-handbook.md) | [PDF](handbooks/blockout-sop-handbook.pdf) | | Motion Previs Studio Operator Handbook | [Markdown](handbooks/motion-previs-studio-sop-handbook.md) | [PDF](handbooks/motion-previs-studio-sop-handbook.pdf) | | Stem Studio Operator Handbook | [Markdown](handbooks/stem-studio-sop-handbook.md) | [PDF](handbooks/stem-studio-sop-handbook.pdf) | | Three-App Windows Workflow Handbook | [Markdown](handbooks/three-app-workflow-handbook.md) | [PDF](handbooks/three-app-workflow-handbook.pdf) | Wasserman Productions verified the handbook submission's links, PDF properties, privacy sanitization, artwork, MCP documentation, and license treatment. The complete editions remain in this repository because their project record, validation history, film walkthrough, and optional external-service material are intentionally broader than the upstream application documentation. Following that scope decision, Gumbii Digital respectfully closed the three unmerged handbook pull requests on 2026-07-16. Closing the proposals preserved their public review records and did not remove the maintained handbook sources or reader PDFs from this repository. Concrete recovery guidance was submitted separately as focused README troubleshooting contributions. [Blockout #4](https://github.com/wassermanproductions/blockout/pull/4), [Motion Previs Studio #3](https://github.com/wassermanproductions/motion-previs-studio/pull/3), and [Stem Studio #4](https://github.com/wassermanproductions/stem-studio/pull/4) remain open for upstream review as of 2026-07-16, with their quality and native macOS/Windows smoke jobs passing. The published handbooks contain no raw test screenshots, desktop backgrounds, recordings, local user paths, hostnames, credentials, control tokens, or personal data. ## Evidence and publication privacy Native test sessions were captured with named screenshots and replayable screen recordings so visual claims could be audited. Those raw captures remain private because a complete desktop recording can expose wallpaper, notifications, window chrome, usernames, file paths, or unrelated personal content. The public record uses non-identifying aggregate results, exact hashes, structured probes, CI URLs, release artifacts, and sanitized document output instead. Every public evidence candidate was scanned for credentials, control data, local paths, machine identity, and archive portability. Any candidate that failed was quarantined and rebuilt before publication. Temporary physical-desktop capture access, listeners, firewall rules, and replay tasks were removed after use. ## Before and after | Surface | Original macOS-oriented baseline | Maintained Windows edition | |---|---|---| | Desktop shell | macOS inset title bar and platform language | Native Windows chrome, hidden application menu, AppUserModelID, File Explorer terminology | | Filesystem | POSIX separators and home/config assumptions | Portable relative paths, drive/UNC handling, junction containment, Windows-safe names | | Media runtime | Development or platform-specific discovery | Packaged, audited FFmpeg/FFprobe with explicit overrides and awaited cleanup | | Model/runtime assets | Development downloads and machine assumptions | Pinned and hashed MediaPipe, yt-dlp, depth, uv/Python, and TIGER assets | | Distribution | macOS packaging | Assisted per-user x64 NSIS, selectable folder, shortcuts, isolated data/uninstall identity | | Supply chain | Application license and project notices | SBOMs, provenance, checksums, asset manifests, modification notices, GPL component source | ## Known limits - The packages are unsigned prereleases; SmartScreen guidance is intentional. Signing, trademark decisions, and the normal commercial third-party review remain separate release gates. - Windows 11 x64 is certified; Windows 10 is best effort. ARM64, ia32, MSI/MSIX, Store delivery, auto-update, and signing are deferred. - Motion downloads a pinned Depth Anything asset on first use. Stem needs internet for its private runtime and model setup; CUDA remains experimental and CPU correctness is the release gate. - Functional and supply-chain evidence does not mean “vulnerability-free.” The current security-alert status and its scope are recorded transparently in [Verification and security](docs/VERIFICATION-AND-SECURITY.md). - Objective media checks do not replace human creative listening, editorial review, or final-mix approval. ## Role and attribution Gumbii Digital maintains the Windows community editions and this consolidated engineering record across product code, runtime integration, packaging, release engineering, compliance, native QA, evidence capture, and publication. Blockout, Motion Previs Studio, and Stem Studio were originally created by **Sam Wasserman / Wasserman Productions**. Application source remains under each upstream repository’s Apache-2.0 terms with original LICENSE, NOTICE, citation, copyright, and in-app credits preserved. Bundled FFmpeg/FFprobe are separately identified GPL components. No upstream endorsement or trademark rights are implied. Original documentation in this repository is licensed under [Apache-2.0](LICENSE). Reproduced application licenses and upstream artwork retain their original terms and attribution; product names and logos are not relicensed as trademarks. ## Source & license This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [GumbiiDigital](https://github.com/GumbiiDigital) - **Source:** [GumbiiDigital/windows-creative-tools-ports](https://github.com/GumbiiDigital/windows-creative-tools-ports) - **License:** Apache-2.0 - **Homepage:** https://github.com/GumbiiDigital/windows-creative-tools-ports Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/mcp-gumbiidigital-windows-creative-tools-ports - Seller: https://agentstack.voostack.com/s/gumbiidigital - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.