bambu-printer-mcp 1.1.6 → 1.1.8

package/CONTRIBUTORS.md

@@ -0,0 +1,26 @@
+# Contributors
+
+Thank you to everyone who builds, tests, reports problems, and shares real printer evidence. This release is stronger because of your work!
+
+## This release
+
+| Contributor | Contribution |
+| --- | --- |
+| [Stenslaen](https://github.com/Stenslaen) | Traces the delayed H2 crash to OTA model detection, documents a multi-day workaround, and reports unexpected state-transition crashes in [#7](https://github.com/DMontgomery40/bambu-printer-mcp/issues/7). |
+| [Alejandro Oñate (alexol91)](https://github.com/alexol91) | Reports the missing machine-template G-code and multi-filament override problems in [#12](https://github.com/DMontgomery40/bambu-printer-mcp/issues/12), with measured output and a proposed fix in [#13](https://github.com/DMontgomery40/bambu-printer-mcp/pull/13). |
+| [var-poro](https://github.com/var-poro) | Supplies P2S firmware/MQTT evidence and regression tests in [#15](https://github.com/DMontgomery40/bambu-printer-mcp/pull/15), plus profile-template resolution and inheritance tests in [#16](https://github.com/DMontgomery40/bambu-printer-mcp/pull/16). |
+| [John Randall (johntrandall)](https://github.com/johntrandall) | Captures A1 job manifests and contributes the SD-root/project-file fix in [#14](https://github.com/DMontgomery40/bambu-printer-mcp/pull/14). |
+| [Kyle Taylor (kyletaylored)](https://github.com/kyletaylored) | Contributes Claude Desktop extension packaging, prompted setup, and the writable-temp-directory fix in [#11](https://github.com/DMontgomery40/bambu-printer-mcp/pull/11). |
+| [Quinn (quinnpertuit)](https://github.com/quinnpertuit) | Investigates P2S transfer routing and contributes model-capability and serial-prefix analysis in [#9](https://github.com/DMontgomery40/bambu-printer-mcp/pull/9). The release uses the alternative P2S implementation from #15. |
+| [Vail (VailElla)](https://github.com/VailElla) | Contributes the native X2D transport, local eMMC investigation, and hardware evidence in [#10](https://github.com/DMontgomery40/bambu-printer-mcp/pull/10). That integration remains under review and is not enabled in this release. |
+
+## Project contributors
+
+Thank you also to the existing contributors whose work this release builds on:
+
+- [David Montgomery (DMontgomery40)](https://github.com/DMontgomery40) — project maintainer.
+- [rowbotik](https://github.com/rowbotik) — printer, AMS, slicing, and operational work across the existing release history.
+- [len-foss](https://github.com/len-foss) — project code contribution.
+- [thebitrock](https://github.com/thebitrock) — project code contribution.
+
+See the [full contribution history](https://github.com/DMontgomery40/bambu-printer-mcp/graphs/contributors) for commit authorship. Credit here includes bug reports and reviewed proposals as well as merged code.

package/README.md

@@ -9,9 +9,9 @@
 
 A Bambu Lab-focused MCP server for controlling Bambu printers, manipulating STL files, and managing end-to-end 3MF print workflows from Claude Desktop, Claude Code, or any MCP-compatible client.
 
-This is a stripped-down, Bambu-only fork of [mcp-3D-printer-server](https://github.com/DMontgomery40/mcp-3D-printer-server). All OctoPrint, Klipper, Duet, Repetier, Prusa Connect, and Creality Cloud support has been removed. What remains is a focused, lean implementation for Bambu Lab hardware.
+Built with help from our [contributors](./CONTRIBUTORS.md). Huge thanks to everyone sharing fixes, careful bug reports, and real printer testing!
 
-Local handoff note: see [REMOTE-DEPLOYMENT.md](./REMOTE-DEPLOYMENT.md) for the custom H2D/H2S/H2C patches, per-printer MCP split, and remote deployment plan used in this clone.
+This is a stripped-down, Bambu-only fork of [mcp-3D-printer-server](https://github.com/DMontgomery40/mcp-3D-printer-server). All OctoPrint, Klipper, Duet, Repetier, Prusa Connect, and Creality Cloud support has been removed. What remains is a focused, lean implementation for Bambu Lab hardware.
 
 ---
 
@@ -19,6 +19,14 @@ Local handoff note: see [REMOTE-DEPLOYMENT.md](./REMOTE-DEPLOYMENT.md) for the c
 
 This fork adds a substantial set of printer control tools beyond the upstream `mcp-3D-printer-server`. Everything listed below is unique to this package.
 
+### v1.1.8 — reliable installs, printer fixes, and Blender MCP
+
+- Fix delayed H2 status crashes and preserve machine-specific G-code when resolving Bambu profiles.
+- Correct P2S and full-size A1 print routing while preserving other models' existing behavior.
+- Install a Claude Desktop extension with prompted settings; keep local credentials and models out of packaged artifacts.
+- Connect to standard Blender MCP servers, discover and call their tools, and verify STL edit/export results.
+- Preserve filament-slot order and isolate temporary files between concurrent jobs and server instances.
+
 ### v1.1.0 — AMS auto-match, camera snapshot, pause/resume, skip objects
 
 - **AMS auto-match by RFID** (`auto_match_ams` on `print_3mf`) — resolves sliced 3MF filament requirements against live AMS inventory. Handles same-SKU different-color filaments. Dry-run with `resolve_3mf_ams_slots`.
@@ -30,10 +38,10 @@ This fork adds a substantial set of printer control tools beyond the upstream `m
 - **HMS diagnostics** (`printer://{host}/hms` MCP resource) — read-only error summary with automatic settle retry.
 - **Utility controls** — `set_print_speed` (silent/standard/sport/ludicrous), `clear_hms_errors`, `reread_ams_rfid`, `set_airduct_mode` (cooling/heating for H2/P2).
 - **H2-family-safe print path** — correct `project_file` format with `ams_mapping2` parallel array, H2 firmware quirks handled.
-- **BambuStudio CLI auto-flatten** (`BAMBU_CLI_FLATTEN=true`) — works around upstream profile inheritance bugs.
+- **BambuStudio CLI auto-flatten** (automatic for BBL profiles) — works around upstream profile inheritance bugs.
 - **Print collar charm** (`print_collar_charm`) — specialized two-color wrapper with fixed tray policy.
 
-### v1.1.1 — AMS dryer control (current)
+### v1.1.1 — AMS dryer control
 
 - **AMS dryer start/stop** (`set_ams_drying`) — sends `print.ams_control` MQTT command. Works on heated AMS units (AMS Pro / AMS-HT). Action: `start` or `stop`, target by AMS index 0–3.
 - Same-SKU different-color fix for `auto_match_ams`.
@@ -100,7 +108,7 @@ This fork adds a substantial set of printer control tools beyond the upstream `m
 - List, upload, and delete files on the printer's SD card via FTPS
 - Capture a JPEG snapshot from the chamber camera. Supports A1, A1 mini, P1S, P1P (TCP-on-6000), and X1, X1C, X1E, P2S, H2, H2S, H2D, H2C, H2D Pro (RTSP via ffmpeg). Requires ffmpeg in PATH for the RTSP path.
 - Upload and print pre-sliced `.gcode.3mf` files with full plate selection and calibration flag control (recommended path — see [docs/SLICING.md](./docs/SLICING.md))
-- Optional single-color auto-slice path via BambuStudio CLI. Set `BAMBU_CLI_FLATTEN=true` to enable a workaround that flattens BBL profile inheritance before invoking the CLI — works around upstream bugs in BambuStudio CLI mode ([#9636](https://github.com/bambulab/BambuStudio/issues/9636), [#9968](https://github.com/bambulab/BambuStudio/issues/9968)). Single-color smoke is verified on H2S/H2D/X1C/P1S; H2C requires Bambu Studio 2.4.0 or newer and should use `BAMBU_MODEL=h2c`, not an H2D fallback. H2D two-color CLI slicing is blocked upstream ([#10408](https://github.com/bambulab/BambuStudio/issues/10408)); use a GUI-sliced `.gcode.3mf` for that workflow. Default off; Path A (GUI-slice) remains the recommended workflow for non-BBL profiles, multi-color H2 jobs, or first-time prints. See [docs/SLICING.md](./docs/SLICING.md).
+- Optional single-color auto-slice path via BambuStudio CLI. BBL profile inheritance and include templates resolve automatically before slicing; missing dependencies stop the slice. Standalone custom configurations remain supported. H2C requires a compatible installed Bambu Studio profile tree and `BAMBU_MODEL=h2c`. The previously documented H2D multi-color CLI limitation remains; use a GUI-sliced `.gcode.3mf` for that workflow. See [docs/SLICING.md](./docs/SLICING.md).
 - Parse AMS mapping from the 3MF's embedded slicer metadata (`Metadata/plate_<n>.json` + gcode filament header) and send it correctly formatted per the OpenBambuAPI spec, with correct H2S/H2D/H2C `ams_mapping2` parallel array format
 - **Auto-match AMS slots by RFID** (`auto_match_ams` flag on `print_3mf`). Resolves required `tray_info_idx` from the sliced 3MF against live AMS inventory. Handles same-SKU different-color filaments by matching on `(tray_info_idx, tray_color)` and tracking already-claimed slots. Dry-run with `resolve_3mf_ams_slots` before printing.
 - Cancel, pause, and resume in-progress print jobs via MQTT
@@ -138,7 +146,7 @@ This fork adds a substantial set of printer control tools beyond the upstream `m
 The fastest way to get started. No global install required:
 
 ```bash
-npx @rowbotik/bambu-printer-mcp
+npx bambu-printer-mcp
 ```
 
 Set environment variables inline or via a `.env` file in your working directory (see [Configuration](#configuration)).
@@ -146,7 +154,7 @@ Set environment variables inline or via a `.env` file in your working directory
 ### Install globally from npm
 
 ```bash
-npm install -g @rowbotik/bambu-printer-mcp
+npm install -g bambu-printer-mcp
 ```
 
 After installation, the `bambu-printer-mcp` command is available in your PATH.
@@ -154,7 +162,7 @@ After installation, the `bambu-printer-mcp` command is available in your PATH.
 ### Install from source
 
 ```bash
-git clone https://github.com/rowbotik/bambu-printer-mcp.git
+git clone https://github.com/DMontgomery40/bambu-printer-mcp.git
 cd bambu-printer-mcp
 npm install
 npm run build
@@ -204,8 +212,12 @@ MCP_HTTP_STATEFUL=true
 MCP_HTTP_JSON_RESPONSE=true
 MCP_HTTP_ALLOWED_ORIGINS=http://localhost
 
-# --- Optional Blender MCP bridge ---
-BLENDER_MCP_BRIDGE_COMMAND=       # Shell command to invoke your Blender MCP bridge executable
+# --- Optional standard Blender MCP server ---
+BLENDER_MCP_COMMAND=uvx          # Executable or full path; no shell command string
+BLENDER_MCP_ARGS='["blender-mcp"]'
+BLENDER_MCP_TIMEOUT_MS=120000
+# Start the matching MCP addon inside Blender.
+# Legacy custom executable bridge (optional): BLENDER_MCP_BRIDGE_COMMAND=
 ```
 
 ### Environment variables reference
@@ -221,7 +233,7 @@ BLENDER_MCP_BRIDGE_COMMAND=       # Shell command to invoke your Blender MCP bri
 | `SLICER_TYPE` | `bambustudio` | No | Slicer to use for slicing operations |
 | `SLICER_PATH` | BambuStudio macOS path | No | Full path to the slicer executable. Alias: `BAMBU_STUDIO_PATH` |
 | `SLICER_PROFILE` | | No | Path to a slicer profile or config file |
-| `TEMP_DIR` | `./temp` | No | Directory for intermediate files |
+| `TEMP_DIR` | private folder under the system temporary directory | No | Intermediate files; each server instance gets its own folder unless explicitly configured |
 | `MCP_TRANSPORT` | `stdio` | No | Transport mode: `stdio` or `streamable-http` |
 | `MCP_HTTP_HOST` | `127.0.0.1` | No | HTTP bind address (HTTP transport only) |
 | `MCP_HTTP_PORT` | `3000` | No | HTTP port (HTTP transport only) |
@@ -229,8 +241,11 @@ BLENDER_MCP_BRIDGE_COMMAND=       # Shell command to invoke your Blender MCP bri
 | `MCP_HTTP_STATEFUL` | `true` | No | Enable stateful HTTP sessions |
 | `MCP_HTTP_JSON_RESPONSE` | `true` | No | Return structured JSON alongside text responses |
 | `MCP_HTTP_ALLOWED_ORIGINS` | | No | Comma-separated list of allowed CORS origins |
-| `BLENDER_MCP_BRIDGE_COMMAND` | | No | Command to invoke Blender MCP bridge |
-| `BAMBU_CLI_FLATTEN` | `false` | No | When `true`, the MCP flattens BBL profile inheritance before invoking the BambuStudio CLI. Workaround for upstream issues [#9636](https://github.com/bambulab/BambuStudio/issues/9636) / [#9968](https://github.com/bambulab/BambuStudio/issues/9968). BBL printers only. Single-color smoke verified on H2S/H2D/X1C/P1S; H2C requires Bambu Studio 2.4.0 or newer. H2D two-color CLI slicing remains blocked by [#10408](https://github.com/bambulab/BambuStudio/issues/10408). See [docs/SLICING.md](./docs/SLICING.md). |
+| `BLENDER_MCP_COMMAND` | | No | Trusted executable for a standard stdio Blender MCP server, e.g. full path to `uvx` |
+| `BLENDER_MCP_ARGS` | `[]` | No | JSON array of server arguments, e.g. `["blender-mcp"]`; no shell parsing |
+| `BLENDER_MCP_TIMEOUT_MS` | `120000` | No | Connection/discovery/call deadline, 100–300000 ms; interrupted edits are never retried automatically |
+| `BLENDER_MCP_BRIDGE_COMMAND` | | No | Legacy custom executable receiving `MCP_BLENDER_PAYLOAD`; separate from the standard MCP integration |
+| `BAMBU_CLI_FLATTEN` | automatic | No | Legacy setting; BBL profile resolution now always runs when profiles contain inheritance or includes. A false/unset value cannot bypass required machine G-code. Standalone custom files without dependencies pass through. See [docs/SLICING.md](./docs/SLICING.md). |
 | `BAMBU_PROFILES_ROOT` | derived from `SLICER_PATH` | No | Override path to the BambuStudio `Resources/profiles` directory used by the CLI flattener. Useful for non-standard installs or dev environments. |
 
 SuperTack can be passed for pre-sliced print jobs, but BambuStudio CLI slicing currently fails fast for `supertack_plate` because the accepted CLI bed identifier is not verified. Use a pre-sliced 3MF for SuperTack until this is confirmed.
@@ -246,7 +261,7 @@ Add this server to your MCP client's config (Claude Desktop, Claude Code, Cursor
   "mcpServers": {
     "bambu-printer": {
       "command": "npx",
-      "args": ["-y", "@rowbotik/bambu-printer-mcp"],
+      "args": ["-y", "bambu-printer-mcp"],
       "env": {
         "PRINTER_HOST": "192.168.1.100",
         "BAMBU_SERIAL": "01P00A123456789",
@@ -273,6 +288,25 @@ Where this config lives depends on your client:
 
 Restart your client after editing the config.
 
+### Alternative: Claude Desktop extension (.mcpb)
+
+You can install this server into Claude Desktop without editing JSON by using the `.mcpb` extension bundle. Download `bambu-printer-mcp.mcpb` from the [latest release](https://github.com/DMontgomery40/bambu-printer-mcp/releases), double-click it, and Claude Desktop's extension wizard will register the server. You'll be prompted for your printer IP, serial number, LAN access code, and printer model -- the same values as the `mcpServers` config above.
+
+If your org has disabled Claude Desktop extension installs, install unpacked instead:
+
+1. Clone the repo and run `npm ci && npm run build`.
+2. Open Claude Desktop -> **Settings** -> **Extensions** -> **Advanced Settings** -> **Extension Developer** -> **Install Unpacked**.
+3. Select the repo's root directory (the one containing `manifest.json`).
+
+To build the bundle yourself instead of downloading a release asset:
+
+```bash
+npm ci
+npm run package:mcpb
+```
+
+This produces `bambu-printer-mcp.mcpb` in the repo root using a pinned packaging tool. Packaging installs production dependencies in a temporary directory, retains licenses and source, excludes local credentials and models, and leaves your development dependencies intact.
+
 ### Recommended: use with codemode-mcp
 
 For any MCP server with a large tool surface, wrapping it behind [codemode-mcp](https://github.com/jx-codes/codemode-mcp) dramatically reduces token usage. Instead of exposing every tool definition to the model (which can consume tens of thousands of tokens per turn), codemode lets the agent write code against a two-tool interface (`search()` and `execute()`), loading only the tools it needs on demand.
@@ -1251,31 +1285,70 @@ These defaults keep you safe when printing downloaded models. When calling `slic
 
 ### Advanced Tools
 
-#### blender_mcp_edit_model
-
-Send a set of named edit operations (remesh, boolean, decimate, etc.) to a Blender MCP bridge command for advanced mesh work that goes beyond what the built-in STL tools support.
+#### Blender MCP
 
-When `execute` is `false` (the default), the tool returns the payload that would be sent without running anything -- useful for previewing what would be dispatched.
+Use a standard stdio Blender MCP server with `BLENDER_MCP_COMMAND` and
+`BLENDER_MCP_ARGS`. For the common Blender MCP server, install `uv` and its
+matching Blender addon, enable the addon, and start its connection inside
+Blender. Set the command to your full `uvx` path and the argument array to
+`["blender-mcp"]`. The Claude Desktop extension also offers these two optional
+settings. Printer tools work without Blender configured.
 
-When `execute` is `true`, the server invokes the configured bridge command with the payload as a JSON-encoded environment variable (`MCP_BLENDER_PAYLOAD`). Configure it with `BLENDER_MCP_BRIDGE_COMMAND`; per-call `bridge_command` overrides require `MCP_ALLOW_EXECUTABLE_ARG=1`.
+1. Call `blender_mcp_status` with `{"connect": true}` to initialize the server
+   and discover its tools and input schemas. A connected MCP server does not
+   by itself prove that the Blender addon is running.
+2. Call `blender_mcp_call` with a discovered tool name and its arguments. The
+   full MCP result, including images and errors, is returned. For example:
 
 ```json
 {
-  "stl_path": "/path/to/model.stl",
-  "operations": ["remesh", "decimate:0.5", "boolean_union:/path/to/other.stl"],
-  "execute": false
+  "tool_name": "get_scene_info",
+  "arguments": {"user_prompt": "Inspect the scene before preparing a print."}
 }
 ```
 
+For advanced Blender operations, forward `execute_blender_code` with `code`
+and the user's original `user_prompt`. These calls may edit the active scene.
+Use the discovered schema rather than assuming a tool exists.
+
+#### blender_mcp_edit_model
+
+The standard MCP edit helper imports an STL, applies ordered edits, and exports
+an STL without replacing the input or an existing output. Supported operations
+are `decimate:<ratio>` (greater than 0 through 1), `remesh:<voxel size>` (positive,
+in STL coordinate units), and `boolean_union:<STL path>`. Other operations can
+use `blender_mcp_call`. Both processes must have access to the same file paths.
+When `BLENDER_MCP_COMMAND` selects standard MCP, the advertised tool schema
+requires an explicit `output_path` for both preview and execution. Legacy-only
+bridge configurations keep `output_path` optional for compatibility.
+
 ```json
 {
   "stl_path": "/path/to/model.stl",
-  "operations": ["remesh"],
-  "bridge_command": "/usr/local/bin/blender-mcp-bridge",
-  "execute": true
+  "output_path": "/path/to/model-edited.stl",
+  "operations": ["decimate:0.5"],
+  "user_prompt": "Reduce the triangle count of this model for printing.",
+  "execute": false
 }
 ```
 
+The default preview returns the plan and generated Python without launching
+Blender. Set `execute` to `true` to run it. A successful standard edit returns
+`output_verified: true`, `output_path`, byte count, and triangle count after
+checking the matching export receipt and a valid finite mesh. The helper
+preserves existing scene objects and requires Object Mode. Inspect the result
+before slicing; a valid STL is not a guarantee of printability.
+
+The bridge enforces request deadlines, closes child connections, and never
+replays interrupted editing requests. After a timeout, inspect Blender before
+trying the edit again because execution may already have started.
+
+Existing custom executables still work through `BLENDER_MCP_BRIDGE_COMMAND`.
+They receive `MCP_BLENDER_PAYLOAD` with the requested file and operations;
+their results explicitly report `output_verified: false`. A missing executable
+configuration is an error when execution is requested. Per-call legacy
+`bridge_command` overrides remain disabled unless `MCP_ALLOW_EXECUTABLE_ARG=1`.
+
 </details>
 
 ---

package/dist/blender-mcp-bridge.d.ts

@@ -0,0 +1,10 @@
+import { type CallToolResult } from "@modelcontextprotocol/sdk/types.js";
+type Arguments = Record<string, unknown>;
+export declare class BlenderMcpBridge {
+    private session;
+    private invoke;
+    status(args: Arguments, signal?: AbortSignal): Promise<unknown>;
+    call(args: Arguments, signal?: AbortSignal): Promise<CallToolResult>;
+    edit(args: Arguments, legacyCommand?: string, signal?: AbortSignal): Promise<unknown>;
+}
+export {};