fnf-blender-mcp 0.2.1 → 0.2.2

package/README.md

@@ -1,27 +1,29 @@
-# Higgsfield use Blender
+# Higgsfield Blender MCP
 
-The independent `fnf-blender-mcp` package in `fnf-local-pluging-bridge-mcp/blender` controls a dedicated background Blender process. No add-on, HTTP listener, WebSocket, cloud account or open Blender window is required.
+Local MCP server that controls a dedicated background Blender process. No add-on, HTTP listener, WebSocket, cloud account or open Blender window is required.
 
 ```text
 Desktop MCP client → stdio → Node MCP → process pipes → Blender --background → bpy
 ```
 
-Each MCP connection owns one process. Its scene persists between commands; it cannot access unsaved work in an already-open desktop Blender. Open saved input with `bl_open_project`, edit and render, then save a `.blend` output to inspect in the desktop UI. Disconnecting loses unsaved session changes. The After Effects package at the repository root is independent.
+Each MCP connection owns one process. Its scene persists between commands; it cannot access unsaved work in an already-open desktop Blender. Open saved input with `bl_open_project`, edit and render, then save a `.blend` output to inspect in the desktop UI. Disconnecting loses unsaved session changes.
 
-## Setup
+## Requirements
 
-Requires Node.js 24+ with npm and Blender 4.2+. Version 0.2.0 introduces the background runtime; version 0.1.0 uses the previous add-on. Install the latest published version (0.2.0 or newer); rerun the install command to update an existing installation.
+- Node.js 24 or later with npm.
+- Blender 4.2 or later on the same computer as the MCP client.
+
+## Installation
 
 ```sh
-npm view fnf-blender-mcp@latest version --registry=https://registry.npmjs.org/
 blenderDir="$HOME/.higgsfield/blender-mcp"
-npm install --prefix "$blenderDir" --registry=https://registry.npmjs.org/ fnf-blender-mcp@latest
+npm install --prefix "$blenderDir" fnf-blender-mcp@latest
 blenderCli="$blenderDir/node_modules/fnf-blender-mcp/dist/cli.js"
 node "$blenderCli" doctor --blender "/absolute/path/to/blender"
 node "$blenderCli" config --blender "/absolute/path/to/blender" --format json
 ```
 
-Use the executable inside `Blender.app/Contents/MacOS/Blender` on macOS, or `blender.exe` on Windows. `config --format toml` prints a Codex entry. Both formats include absolute Node/server paths and `BLENDER_EXECUTABLE`; merge the entry into the intended client and refresh its connection. The helper prints configuration but does not register a server. See the [installation skill](skills/use-blender/references/installation.md) for PowerShell and migration steps.
+Use the executable inside `Blender.app/Contents/MacOS/Blender` on macOS, or `blender.exe` on Windows. `config --format toml` prints a Codex entry. Both formats include absolute Node/server paths and `BLENDER_EXECUTABLE`; merge the entry into the intended client and refresh its connection. The helper prints configuration but does not register a server. The installed package includes a `use-blender` skill with additional setup guidance.
 
 The server starts Blender on its first execution call. `doctor` checks a separate temporary background process and terminates it afterward. Verify conversation access with `bl_health` and `bl_get_scene_summary`. `BLENDER_EXECUTABLE` can be set directly; without it the runtime tries standard installation locations and PATH. No separate Python installation is needed at runtime.
 
@@ -44,29 +46,14 @@ The npm archive contains the Blender craft modules. `bl_list_skills` lists the m
 
 Render a camera frame to PNG; files up to 4 MiB receive an inline preview. Cycles supports sample overrides. Save/render require `overwrite: true` for existing output files; opening a different project refuses unsaved changes unless explicitly discarded. Arbitrary Python is not sandboxed and can bypass these typed-tool guards. Automatic execution of Python embedded in opened `.blend` files is disabled.
 
-## Session lifecycle
+## Troubleshooting and limits
 
 A timed-out job continues and keeps its `job_id`. Query `bl_job_status` before retrying; additional execution commands are rejected while it runs. No automatic retries or rollbacks occur. Status retains at most 128 jobs within the MCP process. If Blender crashes, the session fails and is not restarted automatically: inspect output files before reconnecting to a new empty session. Closing the MCP terminates its child process, including a running job; save needed changes first.
 
-In 0.2.0, `launch`, `install-addon`, `bl_screenshot`, bridge discovery, PID selection and runtime-directory overrides are removed. Use camera renders for visual evidence. No existing desktop scenes, preferences or installed add-ons are modified during startup. Multiple MCP connections have separate background scenes.
-
-## Development and validation
-
-From the repository root:
-
-```sh
-cd blender
-npm ci
-npm test
-npm run typecheck
-npm run test:package
-BLENDER_EXECUTABLE=/absolute/path/to/blender npm run test:live
-```
-
-Offline tests exercise actual MCP and child-process pipes using a Python CLI fixture, persistent session state, isolation, timeout recovery, process death, bounded results/history, output formatting, CLI configuration and typed-script guards. They do not replace live Blender validation. `test:package` installs the archive independently and verifies 21 tools, offline guidance, asset lookup and the absence of runtime add-on files. `test:live` uses real Blender for geometry, materials, keyframes, file guards and a small Cycles render in disposable files.
+Use camera renders for visual evidence. No existing desktop scenes, preferences or installed add-ons are modified during startup. Multiple MCP connections have separate background scenes.
 
 Verified on macOS arm64 with Blender 4.2.23 LTS: persistent scene, mesh/material/camera/light edits, keyframes, save/reopen guards and a Cycles PNG preview. Windows/Linux native Blender execution has not been verified locally.
 
-See [RELEASING.md](RELEASING.md) for release steps. The setup skill is mirrored in fnf-mcp-server's `/use-blender` command; keep its body and references synchronized. See [UPSTREAM.md](UPSTREAM.md) for provenance and [LICENSE](LICENSE) for the MIT license.
+The installed package includes `UPSTREAM.md` and `LICENSE` for provenance and licensing details.
 
 Background Blender does not reliably mark direct Python edits as dirty. The MCP also tracks attempted mutations, including failed commands and arbitrary `bl_execute` calls, conservatively as unsaved until `bl_save_project` or an explicitly permitted `bl_open_project` succeeds. Read tools preserve this state.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "fnf-blender-mcp",
-  "version": "0.2.1",
-  "description": "Higgsfield use Blender: local stdio MCP controlling a background Blender process without add-ons.",
+  "version": "0.2.2",
+  "description": "Local MCP server for Blender with a background process and offline creative skills.",
   "type": "module",
   "license": "MIT",
   "engines": {
@@ -15,7 +15,6 @@
     "dist",
     "skills",
     "README.md",
-    "RELEASING.md",
     "UPSTREAM.md",
     "LICENSE",
     "scripts/*.py"
@@ -42,20 +41,11 @@
     "access": "public",
     "registry": "https://registry.npmjs.org/"
   },
-  "homepage": "https://www.npmjs.com/package/fnf-blender-mcp",
   "keywords": [
     "blender",
     "mcp",
     "higgsfield",
     "3d",
     "bpy"
-  ],
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/higgsfield-ai/fnf-local-pluging-bridge-mcp.git",
-    "directory": "blender"
-  },
-  "bugs": {
-    "url": "https://github.com/higgsfield-ai/fnf-local-pluging-bridge-mcp/issues"
-  }
+  ]
 }

package/RELEASING.md

@@ -1,11 +0,0 @@
-# Release fnf-blender-mcp
-
-Run commands from this `blender/` directory. Its package and lockfile are independent of After Effects.
-
-1. Run `npm ci`, `npm test`, `npm run typecheck`, `npm run test:package`, and `test:live` with a real `BLENDER_EXECUTABLE` when available.
-2. Version 0.2.1 bundles the Blender craft skills, including the additions from PR #25. Verify that it is unpublished with `npm view fnf-blender-mcp versions --json`. Never overwrite an existing npm version; bump both manifests for subsequent releases.
-3. Keep README.md, skills/use-blender and the fnf-mcp-server command bundle on `fnf-blender-mcp@latest`; preserve historical migration versions. Review migration instructions for removed commands and tools.
-4. Merge the source changes and version metadata into `main`, check out its exact commit in a clean worktree, rerun the checks, then run `npm pack --json`, review the contents, then publish the reviewed archive with `npm publish ./fnf-blender-mcp-0.2.1.tgz --access public --registry=https://registry.npmjs.org/` when publication is authorized.
-5. Verify the public version and checksum and test a fresh registry installation. Publish the package before deploying the fnf-mcp-server instructions that require it.
-
-Merging the source MR does not publish npm. Version 0.1.0 still requires the old add-on; it is not a fallback for 0.2.0 setup. New clients need a refreshed configuration containing BLENDER_EXECUTABLE. Existing desktop files and add-ons are not removed by this release.