Creator Works MCP 2.7.7

Creator Plugins catalogue and import reliability update.

• Refresh and validate the shared community catalogue before downloading or sending a package to Unity.
• Keep pending-import status visible when returning from Unity, and clear obsolete warnings when starting a new action.
• An unchanged package is no longer rejected just because an approval took longer than the catalogue cache timeout. Changed or withdrawn listings still require fresh approval.
• Unity catalogue helper 0.1.3 correctly handles listings without downloadable archives, including OptiC's Warehouse Loft. All apps and the Unity window use the same community catalogue.
• Exact known older Unity helpers can be upgraded with backups. User-modified helpers are not overwritten.

Existing Unity projects need their catalogue helper updated through Add Unity menu to receive the Unity-side changes. Updating the desktop app alone does not overwrite project files.

Validation included real native Unity package cancellation and retry on Unity 2022.3 and Unity 6 using disposable text-asset fixtures. This does not guarantee every community package is safe or compatible with every project. Back up your project before importing.

Windows, macOS Apple silicon, macOS Intel and Linux packages are provided. macOS packages use ad-hoc signing, not Apple notarization; platform security prompts may still appear.

Creator Works MCP 2.7.6

Creator Works MCP 2.7.6 adds suite terms acknowledgement and contextual help, rejects invalid Visual Scripting graph connections, updates audited dependencies, and packages macOS Apple silicon and Intel builds. The exact Windows x64 draft passed clean install and upgrade-from-2.7.4 tests, including busy private-runtime refusal and preservation of settings, user content, and unrelated Node processes. Both macOS DMGs passed architecture and ad-hoc signature checks. Windows packages are unsigned; macOS packages are not Apple-notarized. macOS/Linux Unity workflows still need native user acceptance. The standalone ZIP remains available for manual Node.js 20+ deployments. See SHA256SUMS.txt for asset checksums.

Creator Works MCP 2.7.4

Creator Works MCP packages the server, Unity bridge, and a private Node.js 24 LTS runtime for Windows, Linux, and macOS. Windows packages are unsigned and macOS packages are not notarized. Save your work and close MCP clients if Setup asks. The standalone ZIP remains available for manual Node.js 20+ deployments. See the tagged README and version-specific release notes for benefits, profile choices, and acceptance limits.

Creator Works MCP 2.7.2

Windows update: fixes Add Unity menu remaining blocked by a stale Unity lock file. Plugins gains preview galleries, streamed large-package downloads, progress and cancellation. Hub integration requires Creator Hub 0.1.7 or newer. Standalone use remains available.

Installed upgrades, runtime preservation and native prompt checks. Package integrity checks do not establish code safety.

Creator Works MCP 2.7.1 - Windows runtime update hotfix

Creator Works MCP 2.7.1

Windows hotfix for updates blocked by lingering private Node processes.

• MCP exits when its AI client disconnects, including during a pending Unity
  compile wait. Already-dispatched Unity work is not cancelled or sent twice.
• A blocked standalone installer offers Yes: disconnect, No: recheck,
  or Cancel. It targets only this installation's verified private runtimes.
• Creator Hub 0.1.3 or newer provides the same confirmed disconnect before
  updating MCP. Update Hub first, or use this standalone Windows installer.
• Other Node processes, AI applications, settings and Unity projects are not
  force-closed or removed. If a client reconnects, pause its MCP connection and
  retry. There is no repeated process-kill loop.

Upgrade

Save ongoing work. Run Creator.Works.MCP_2.7.1_x64-setup.exe, or use Update app
in Hub 0.1.3 or newer. Approve disconnect only when ready to stop the active MCP
connections. Reconnect your AI client after the update. Do not uninstall, delete
app data, or close every Node process in Task Manager.

Verification

The exact installer passed upgrades from 2.6.0, 2.7.0-alpha.1,
2.7.0-alpha.2 and 2.7.0 on disposable Windows runners. Tests cover two active
private runtimes, refusal without consent, scoped cleanup, unrelated-process
preservation, settings/content preservation, installed payload hashes, EOF during
idle and pending work, connected usability, and busy uninstall refusal.

• Build and four-baseline acceptance
• Native Yes/No/Cancel and app lifecycle acceptance

Native prompt interaction and the subsequent guarded silent installation were
tested separately. This is not a claim of a complete interactive installer wizard
test, every historical installer, every AI client's reconnect policy, or a new
macOS/Linux release. Alpha.2 is a pinned CI baseline. The Windows installer is
not Authenticode signed; signed Hub metadata and SHA-256 checksums verify the
published bytes separately. Original acceptance reports and limits are attached.

Creator Works MCP 2.7.0

Creator Works MCP 2.7.0

Windows update for the coordinated Creator Hub release. MCP remains a standalone
app as well as a compatible Hub tool, using the same saved projects and settings.
Linux/macOS packages stay on the separate 2.6.0 release track.

New and Improved

• Creator Plugins: browse shared community contributions, previews, authors,
  requirements and usage notes. Supported Unity packages can be sent to a
  selected project for review. AI skills, MCP tools and instructions-only items
  are not imported into Unity as executable assets.
• Unity menu: browse from Creator Plugins > Browse inside Unity. Imports
  still use Unity's file-selection dialog. Code warnings stay visible.
• Clear import outcomes: queued, under review, cancelled, failed and imported
  are distinct states. A restart does not invent a successful outcome or retry.
• Retry without losing history: an explicit retry creates a new request.
  Completed requests move to history; their final receipts remain unchanged.
  Unity and desktop apps share a nonblocking queue lock and a 100-pending limit.
  Missing or malformed receipts never count as completed imports.
• Known-helper upgrades: the exact supported older Unity menu can be updated
  after closing its project. The complete old folder is backed up, Unity metadata
  is retained, and custom or unexpected files block replacement.
• Safer app upgrades: installer checks refuse busy installed components.
  Settings and unrelated content are retained. No unrelated Node or AI processes
  are force-closed.
• Shared presentation: compact navigation and the Creator Plugins icon match
  the suite, with accessible navigation and original dependency notices included.

Upgrade

1. Save work. In Creator Hub, choose Update app for MCP, or run the direct Windows
   installer from this release.
2. Close active MCP clients or the app when requested, then retry. Do not uninstall
   or delete application data as a normal upgrade step.
3. Reopen MCP and check your saved project list. Update project bridges only where
   needed. Close the selected Unity project before updating its Plugins menu.
4. Reopen Unity and reconnect the AI client. Confirm bridge status before editing.

Package imports remain optional and require your review. Checksums verify bytes,
not code safety. C# can run during Unity import; read the contributor's source and
requirements before proceeding. Imports do not automatically save your scenes.

Checks and Limits

Source validation covers Unity 2022.3.39f1 and 6000.3.21f1: each passed 193 queue
and helper checks, 10 restart/callback checks, and 101 offline protocol/lock checks.
The lock checks include actual cross-process Windows Rust/C# exclusion and release.
An actual small C# package also passed import, compilation, domain reload and
fresh-process reopen in both Editors, with its final receipt unchanged.
They do not establish native macOS/Linux interoperability or actual package-import
acceptance for every plugin.

The Windows installer acceptance matrix uses one exact candidate against 2.6.0,
2.7.0-alpha.1 and the pinned accepted alpha.2 CI artifact. It checks busy-runtime
refusal, cooperative exit, exact installed payloads, settings and unmanaged-file
preservation. Publication is gated on that matrix and coordinated Hub checks;
see the release's verification attachments for the final artifacts and results.
Alpha.2 is a CI baseline, not a claimed public release.

The exact Windows installer passed all three upgrade baselines in
build and installed acceptance.
The same installed executable passed the approved logo and native busy/idle close
checks in a separate replay.
That replay was not wholly green: its historical alpha.2 clean-install fixture
stopped before the new installer ran. The old guard then succeeded in a diagnostic
probe after 15.578 seconds, beyond the installer's 15-second limit. A slow preflight
is a hypothesis, not a confirmed root cause or a claimed fix. Safety timeouts were
not relaxed. The verification attachments preserve both passing and failing evidence.

These checks do not replace the separate final through-Hub acceptance. Managed
updates require Creator Hub 0.1.0 or newer; MCP can still be used standalone.

The installer remains unsigned by a Windows publisher. Signed Hub metadata and
SHA-256 checksums are separate from Authenticode signing. Unknown or duplicate
installations still need explicit selection rather than automatic removal.

Existing token-efficient profiles, focused documentation, and bounded scene
responses remain. This release claims no new end-to-end token or quota savings.
Unity compile/build checks do not prove headset, hosted loading, interaction or
multiplayer behavior. Verify those in your actual project.

Creator Works MCP 2.7.0-alpha.1 - Creator Hub Preview

Creator Works MCP 2.7.0-alpha.1

Windows test release for the coordinated Creator Hub preview. No stable/main
promotion. The existing Unity tools, SDK profiles, Visual Scripting knowledge,
and token-aware reference/response limits remain available.

New in This Preview

• Compact shared Creator interface and accessible app switcher.
• Normal MCP controls inside a compatible Creator Hub, after an explicit native
  approval prompt. Uses the installed app's resources and existing settings;
  it is not a second, disconnected project list.
• Standalone MCP remains usable without Hub. Installing Hub does not rewrite
  shortcuts, import projects automatically, or stop healthy MCP clients.
• Guarded Windows NSIS upgrade path, including paths containing spaces. Active
  launcher/runtime checks refuse unsafe updates instead of force-closing them.
• Signed release metadata for Hub to verify downloads and the actual installed
  launcher. This is separate from Windows publisher signing; the EXE is unsigned.
• Bundled original dependency notices and inventories in licenses: Rust,
  locked production Node packages, Lucide/Feather, and source/brand notices.
  The private Node runtime also keeps its own full license beside the executable.

Test It

1. Install Creator Hub 0.1.0-alpha.3 once and enable Include prereleases. No separate MCP download or Project Setup installation is needed.
2. Select Creator Works MCP and choose Install app or Update app.
3. Save work and close active MCP clients if requested. Do not remove settings.
4. Choose Open hosted development preview, then approve Enable MCP controls.
5. Verify your project list and selected project. Update project bridges explicitly
   only where needed, reopen Unity, reconnect the AI client, and check bridge status.

The direct Windows installer remains available for standalone use. Older MSI,
unknown, duplicated, and custom-location installations may need a separate
reviewed migration; the preview does not silently overwrite or remove them.

Acceptance and Limits

The Windows acceptance artifact tests the real 2.6.0 to preview NSIS update,
blocked active-runtime updates, cooperative exit, exact installed payload/license
hashes, preserved settings/unmanaged-file sentinels, and busy-uninstall refusal.
The release uses those tested installer bytes, not a tag-triggered rebuild.
Passed: Windows installed upgrade acceptance
and server/launcher regression tests.
The attached release-verification.json and installed-acceptance.json record
the exact source revision, artifact hashes and test boundaries.

Passed: Hub native integration acceptance,
including MCP-only 2.6.0 upgrade, valid saved project/selection preservation,
writable hosted settings, native consent and actual busy-close refusal. This
uses the final signed public installers, not browser mocks. A higher-version
Hub self-update remains untested and is separate from this MCP upgrade result.
An opaque settings sentinel is not proof of every historical configuration
migration. Full installer rollback, automatic shortcut adoption, idle handoff
of an already-open app, and native macOS/Linux Hub hosting are not promised.

There is no new measured token-saving percentage in this preview. Existing
token-efficiency behavior remains; no end-to-end account/quota savings are claimed.
Unity compilation, SDK behavior, manual scene preservation, and headset/multiplayer
results still need testing in the user's actual project.

Creator Works MCP 2.6.0 - Token Efficiency, Feedback and Bridge Fixes

Creator Works MCP 2.6.0

The first token-efficiency release is now on the stable line, with corrections
from architectural scene work and Forest bridge feedback. This is a new build,
not a relabelled 2.6.0-rc.1 installer.

Benefits

• New setups use 25 core tools instead of all 53; existing Full choices remain Full.
• Focused reference lookup carries the manual corrections, without repeatedly loading whole catalogs. Specialist profiles and full references remain available.
• Bounded scene/component/console/compiler replies preserve errors, freshness and omissions.
• Deep active-scene hierarchies are no longer silently cut off after depth 10. Completeness and response-limit metadata are visible before data.
• Create/modify replies include observed world/local transforms rather than relying only on the requested values. Legacy request summaries are labelled; measurements describe the immediate post-apply state, not later physics or hosted behavior.
• Compile waits survive reload. Long commands retain a dispatch record even while Unity blocks the pipe/heartbeat. Poll the original ID, do not duplicate a build. The newest 200 status records are retained; a dispatch receipt is not proof of build completion or continued liveness.
• Local feedback and optional usage check-ins help collect real-world evidence without telemetry or account access.
• The launcher can check for newer stable releases. Automatic metadata checks are optional; installation and bridge updates remain manual.
• Updated the existing Hono pin to 4.13.5, which contains upstream security fixes. No additional runtime dependency was introduced.

Optional Feedback

Enable Local feedback for selected project in the launcher, or explicitly
authorize project_feedback configuration. The file is
.bantworks-mcp/feedback/MCP_FEEDBACK.md, outside Unity's compiled assets.
Notes include MCP/bridge versions when the bridge version is available, plus
the bounded facts supplied by the caller. They do not include project contents,
screenshots, account credentials, or private logs automatically.

Usage check-ins are a separate opt-in: the AI calls task_complete at a genuine
task boundary, and the tool returns a suggested optional question only after at
least five unique tasks and 24 hours. Skip freely. Recording usage requires
explicit consent for that report. The file stays local until its owner chooses
to share it; inspect and redact it first. This is voluntary feedback, not billing
measurement or a token-saving guarantee.

Upgrade

1. Back up work and save/close projects whose bridge you will update.
2. Install the matching release package. Close MCP clients if the private runtime is locked; Setup never force-closes them.
3. Open the launcher and use Update Bridges deliberately for your projects.
4. Reopen Unity, allow compilation, and reconnect the MCP client.
5. Check the selected project, bridge version 2.6.0, and intended capability profile.

Windows x64 EXE, Linux x86_64 AppImage/DEB/RPM, macOS Apple Silicon DMG, and the
standalone Node.js ZIP are published with SHA-256 checksums. Windows remains
unsigned and macOS is not notarized; checksums prove integrity, not publisher
identity. Existing app identity/settings migration are preserved.

Evidence and Limits

Local automated checks cover the server, launcher settings, consent/disabled
states, task deduplication and cooldown, update metadata validation, and retained
command correlation: 195 Node tests and 23 Rust tests passed, with a clean npm
audit and isolated bundled-server smoke. The frontend passed headless Edge
checks at 900 and 560 pixels using mocked native IPC/GitHub responses; this is
not a clean installed-app upgrade test. Disposable Unity 2022.3.39f1 and 6000.3.21f1 fixtures exercise
32-level hierarchy export, scaled-parent transform receipts, parent following,
and a blocking menu with readable dispatch status. These are Editor fixtures,
not hosted Forest or headset acceptance of the release.

Measured tool schemas: core 23,172 bytes; Full 48,613 bytes, about 52% less for
core. Results do not establish whole-task token, cost, quota or latency savings.
New optional feedback adds one tool; Full functionality remains available.

General hierarchy pagination, batch bounds, rename/cutaway tooling, safe background
installer downloads, render-pipeline conversion, one-click SDK installation,
manual-edit conflict control and the player emulator are not part of this release.
Shader Graph mutation remains experimental. The reported child-following failure
was not reproduced in the fixture; no speculative reparenting change was made.

Thanks to FireRat for the included cross-platform packaging and test-policy
contributions, and to people supplying concrete project feedback. No private
feedback journal or user project files are included in the release.

Creator Works MCP 2.6.0-rc.1 - Token Efficiency and Multiplatform Preview

Creator Works MCP 2.6.0-rc.1

Prerelease for testing. Stable users can stay on
2.5.1.
This candidate focuses on token efficiency, accurate scene inspection, and
Editor reload handling, with multiplatform packaging and test-run controls.

Expected Benefits

• Less initial AI context: new configurations use the 24-tool core profile instead of all 52 tools. Measured schema text is 21,827 versus 47,268 UTF-8 bytes, about 54% smaller. This is not a 54% reduction in total tokens, cost, or account usage.
• Read the relevant documentation, not the entire library: get_mcp_reference searches local manual, component, JavaScript, and workflow entries, including corrections and continuation details. Full documents remain available explicitly. No paid retrieval service, embeddings database, or new runtime dependency is required.
• Avoid oversized replies: hierarchy, component, console, import, compiler, and prefab reads default to a 64 KiB compact response-text budget. Counts, omissions, errors, and freshness remain visible; callers can filter or explicitly raise the budget up to 4 MiB.
• Keep all capabilities when needed: Full retains all 52 tools and benefits from focused references and bounded reads. Smaller profiles hide specialist tools until the profile is changed and the client reconnects. Existing saved Full selections are preserved.
• Reduce avoidable inspection/retry loops: request identity-only component inventories and selected properties, wait through Editor reloads, and resume pending commands using their exact project-bound polling instructions.

Scene and Editor Reliability

• componentDetails: "identity" avoids serializing component properties. Field-only and filtered fresh reads use targeted queries rather than a full state export.
• Missing requested properties are reported as missingProperties, not mistaken for false. Fresh queries support hidden/nested serialized paths and bounded renderer enabled/material summaries.
• Compile waits tolerate domain reload within the caller's deadline and require a fresh, settled Editor. Stale diagnostics alone cannot report successful readiness.
• Menu/query timeouts retain command and project identity plus polling arguments. A timeout does not cancel an operation; do not resubmit a pending mutation.
• Automatic full-scene exporting remains disabled by default in Edit and Play mode. Explicit refresh still works; Unity object access remains on the main thread.

Launcher and Packaging

• Optional restriction on unfiltered Unity test runs. The default remains permissive for compatibility; the Unity policy is project-scoped and survives domain reload.
• Launcher, CLI, and PowerShell setup preserve existing setting fields. Malformed settings fail without being replaced, and the UI reports persistence failures.
• Packages: Windows x64 setup EXE; Linux x86_64 AppImage, DEB, and RPM; macOS Apple Silicon DMG; and a standalone Node.js 20+ ZIP.
• Launcher packages include a private Node.js 24 LTS runtime. The standalone ZIP requires your own Node.js and includes Windows and Unix setup entry points.
• Release checksums use the actual uploaded filenames and reject missing platforms, incomplete uploads, or invalid digests.

Upgrading and Testing

1. Back up your Unity project and client configuration. Save and close the projects whose bridges you plan to update.
2. Install the matching package. On Windows, close Creator Works MCP and MCP clients if Setup reports that its private runtime is in use; Setup does not force-close them.
3. Check imported projects and your selected tool profile. Existing Full configurations stay Full; new ones default to Token Saver. Use Full or a specialist profile for graph authoring and testing.
4. Use Update Bridges for the projects you intend to test, reopen Unity, and let it compile. Installing the launcher alone does not prove a project bridge was refreshed.
5. Reconnect the MCP client, call get_bridge_status, and verify the project identity, candidate bridge version, and fresh readiness before editing.
6. Try your normal scene and graph tasks. Check missing-property diagnostics, compile/reload recovery, pending-command polling, and Editor responsiveness. Report the version, profile, SDK, reproduction, and observed result without sharing credentials or private project content.

Unsigned distribution: the Windows EXE is unsigned and the macOS app is not
notarized, so OS security warnings are expected. Compare your download with
SHA256SUMS.txt. A checksum verifies integrity, not publisher identity.

Verification and Limits

• Local candidate checks passed: 182 Node tests, 21 Rust launcher tests, version synchronization, standalone protocol/reference and archive smoke tests, Windows NSIS build, and zero reported npm audit vulnerabilities.
• The bridge passed compile/command fixtures in disposable Unity 2022.3.39f1 and 6000.3.21f1 projects. These exercised targeted property reads, no full-snapshot rewrites for those queries, and isolated test-policy persistence/guard behavior. The policy check is not a full Test Runner execution.
• GitHub Actions records the combined candidate's CI and packaging checks. Building a package is not proof of clean installation or everyday operation on that platform.
• Candidate clean-install/upgrade, real-project tasks, large-project performance, and end-to-end token/latency measurements remain acceptance work before stable release. Earlier local test builds are not evidence that this exact candidate was installed.
• Shader Graph mutation is experimental. Hosted loading, headset interaction/performance, and multiplayer need real-client testing; Editor/build checks cannot confirm them.

Contributor Credit

Thanks to FireRat666 for
PR #27: Multiplatform builds
and PR #28: Add setting to restrict unfiltered test runs.
Their original commits and authorship are retained. This candidate adds focused
policy persistence/error handling and checksum validation around that work.

Not Included Yet

Compact embedded-graph inspection, guarded batch graph editing, graph artifact
handles, revision/delta replies, and stronger mixed manual/MCP edit conflict
handling remain future work. Creator SDK installation and Unity AI
interoperability are separate planned tracks; the player emulator stays last.
Render-pipeline conversion is not included. No project-specific game content
or private feedback journals are shipped.

Publication Record

All six downloadable packages were retrieved and their SHA-256 values verified against both the consolidated checksum file and GitHub upload digests. All platform build jobs and the six integration CI checks passed. The final draft-only asset-label lookup was completed manually after the workflow returned HTTP 404; the automation fix and regression test are on master. The application artifacts and release tag were not changed by that follow-up.

Creator Works MCP 2.5.1

Creator Works MCP 2.5.1 is the guarded Windows installer hotfix for 2.5.0.

Fixed

• Added a pre-install runtime guard that matches only Creator Works MCP's bundled server/runtime/node.exe, preventing opaque locked-file failures during EXE upgrades.
• Interactive upgrades explain which applications to close and offer Retry or Cancel without force-closing user processes. Unattended upgrades exit with code 10 while the runtime is locked.

Changed

• Stable releases now publish one guided NSIS setup executable plus the standalone ZIP and checksums. The unguarded MSI is no longer published.
• Removed the stale Shader Graph Preview suffix from the Windows application title while retaining the experimental feature label inside the launcher.

Upgrade note

• Save your work and fully close Creator Works MCP, Codex, Claude Code, and other connected MCP clients if Setup asks.
• For the one-time move from the 2.5.0 MSI to the 2.5.1 EXE, close MCP clients and remove the old MSI installation before using the guarded EXE upgrade path.
• The Windows installer is currently unsigned. Verify downloads with SHA256SUMS.txt.

Verified

• 137 Node tests and 13 native launcher tests passed.
• The unsigned NSIS installer was built with the private Node.js 24.17.0 runtime.
• An isolated NSIS harness returned 10 while the exact bundled runtime was locked and 0 after it closed; unrelated Node paths did not match.
• The standalone ZIP requires Node.js 20 or newer.