bambu-printer-mcp 1.0.1 → 1.0.2

package/README.md

@@ -9,7 +9,7 @@
 
 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, correct implementation for Bambu Lab hardware -- with two protocol-level bugs fixed that exist in the parent project.
+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.
 
 <details>
 <summary><strong>Click to expand Table of Contents</strong></summary>
@@ -25,8 +25,7 @@ This is a stripped-down, Bambu-only fork of [mcp-3D-printer-server](https://gith
   - [Install from source](#install-from-source)
 - [Configuration](#configuration)
   - [Environment variables reference](#environment-variables-reference)
-- [Usage with Claude Desktop](#usage-with-claude-desktop)
-- [Usage with Claude Code](#usage-with-claude-code)
+- [Usage](#usage)
 - [Enabling Developer Mode (Required)](#enabling-developer-mode-required)
 - [Finding Your Bambu Printer's Serial Number and Access Token](#finding-your-bambu-printers-serial-number-and-access-token)
 - [AMS (Automatic Material System) Setup](#ams-automatic-material-system-setup)
@@ -56,7 +55,7 @@ This is a stripped-down, Bambu-only fork of [mcp-3D-printer-server](https://gith
 
 **What this is not.** This package intentionally supports only Bambu Lab printers. It does not include adapters for OctoPrint, Klipper (Moonraker), Duet, Repetier, Prusa Connect, or Creality Cloud. If you need multi-printer support, use the parent project [mcp-3D-printer-server](https://github.com/DMontgomery40/mcp-3D-printer-server) instead.
 
-**Why a separate package?** The parent project carries all printer adapters in a single binary. When working exclusively with Bambu hardware, that breadth adds noise and includes code paths with known Bambu-specific bugs. This fork strips the project to its Bambu core and applies two targeted protocol fixes described in [Bambu Communication Notes](#bambu-communication-notes-mqtt-and-ftp).
+**Why a separate package?** The parent project carries all printer adapters in a single binary. When working exclusively with Bambu hardware, that breadth adds unnecessary weight. This fork strips the project to its Bambu core for a smaller, faster install. Both packages share the same protocol fixes and safety features.
 
 **Note on resource usage.** STL manipulation loads entire mesh geometry into memory. For large or complex STL files (greater than 10 MB), these operations can be memory-intensive. See [General Limitations and Considerations](#general-limitations-and-considerations) for details.
 
@@ -182,48 +181,9 @@ BLENDER_MCP_BRIDGE_COMMAND=       # Shell command to invoke your Blender MCP bri
 
 ---
 
-## Usage with Claude Desktop
+## Usage
 
-Edit your Claude Desktop configuration file. On macOS this is at `~/Library/Application Support/Claude/claude_desktop_config.json`. On Windows it is at `%APPDATA%\Claude\claude_desktop_config.json`.
-
-**Using npx (recommended -- always runs the latest version):**
-
-```json
-{
-  "mcpServers": {
-    "bambu-printer": {
-      "command": "npx",
-      "args": ["-y", "bambu-printer-mcp"],
-      "env": {
-        "PRINTER_HOST": "192.168.1.100",
-        "BAMBU_SERIAL": "01P00A123456789",
-        "BAMBU_TOKEN": "your_access_token",
-        "BAMBU_MODEL": "p1s"
-      }
-    }
-  }
-}
-```
-
-**Using a globally installed binary:**
-
-```json
-{
-  "mcpServers": {
-    "bambu-printer": {
-      "command": "bambu-printer-mcp",
-      "env": {
-        "PRINTER_HOST": "192.168.1.100",
-        "BAMBU_SERIAL": "01P00A123456789",
-        "BAMBU_TOKEN": "your_access_token",
-        "BAMBU_MODEL": "p1s"
-      }
-    }
-  }
-}
-```
-
-**With slicer configured (for auto-slice and print_3mf workflows):**
+Add this server to your MCP client's config (Claude Desktop, Claude Code, Cursor, Codex CLI, or any MCP-compatible client). The config format is the same everywhere -- an `mcpServers` entry with the command and env vars:
 
 ```json
 {
@@ -244,53 +204,29 @@ Edit your Claude Desktop configuration file. On macOS this is at `~/Library/Appl
 }
 ```
 
-After editing the file, restart Claude Desktop. You should see the bambu-printer tools appear in the tool list when you open a new conversation.
+Where this config lives depends on your client:
 
----
+| Client | Config location |
+|--------|----------------|
+| Claude Desktop (macOS) | `~/Library/Application Support/Claude/claude_desktop_config.json` |
+| Claude Desktop (Windows) | `%APPDATA%\Claude\claude_desktop_config.json` |
+| Claude Code (project) | `.mcp.json` in project root |
+| Claude Code (global) | `~/.claude/settings.json` |
+| Cursor | MCP settings in Cursor preferences |
+| Codex CLI | MCP config per Codex docs |
 
-## Usage with Claude Code
+Restart your client after editing the config.
 
-In Claude Code, MCP servers are configured in your project's `.mcp.json` file or in your global Claude Code settings at `~/.claude/settings.json`.
+### Recommended: use with codemode-mcp
 
-**Project-level configuration (`.mcp.json` in your project root):**
+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.
 
-```json
-{
-  "mcpServers": {
-    "bambu-printer": {
-      "command": "npx",
-      "args": ["-y", "bambu-printer-mcp"],
-      "env": {
-        "PRINTER_HOST": "192.168.1.100",
-        "BAMBU_SERIAL": "01P00A123456789",
-        "BAMBU_TOKEN": "your_access_token",
-        "BAMBU_MODEL": "p1s",
-        "SLICER_TYPE": "bambustudio",
-        "SLICER_PATH": "/Applications/BambuStudio.app/Contents/MacOS/BambuStudio"
-      }
-    }
-  }
-}
-```
+Anthropic and Cloudflare independently demonstrated this pattern reduces MCP token costs by up to 98%:
 
-**Global configuration (`~/.claude/settings.json`):**
+- [Code execution with MCP](https://www.anthropic.com/engineering/code-execution-with-mcp) (Anthropic)
+- [Code Mode: give agents an entire API in 1,000 tokens](https://blog.cloudflare.com/code-mode-mcp/) (Cloudflare)
 
-```json
-{
-  "mcpServers": {
-    "bambu-printer": {
-      "command": "npx",
-      "args": ["-y", "bambu-printer-mcp"],
-      "env": {
-        "PRINTER_HOST": "192.168.1.100",
-        "BAMBU_SERIAL": "01P00A123456789",
-        "BAMBU_TOKEN": "your_access_token",
-        "BAMBU_MODEL": "p1s"
-      }
-    }
-  }
-}
-```
+This applies to all MCP servers, not just this one.
 
 ---
 
@@ -464,7 +400,7 @@ Bambu Lab printers do not use a conventional REST API. Instead, they expose two
 
 ### What this fork fixes
 
-The parent project (`mcp-3D-printer-server`) contains two Bambu-specific protocol bugs that this fork corrects.
+Both this package and the parent project (`mcp-3D-printer-server`) include fixes for two protocol-level issues in the underlying `bambu-js` library.
 
 **Bug 1: FTP double-path error in bambu-js.**
 
@@ -489,7 +425,7 @@ private async ftpUpload(host, token, localPath, remotePath): Promise<void> {
 
 **Bug 2: AMS mapping format in the project_file MQTT command.**
 
-The `bambu-js` library's project file command hardcodes `use_ams: true` and does not support the `ams_mapping` field at all. Separately, the parent project constructs the mapping as a simple array of slot indices (e.g., `[0, 2]`), which does not match the OpenBambuAPI specification.
+The `bambu-js` library's project file command hardcodes `use_ams: true` and does not support the `ams_mapping` field at all. Without the fix, the mapping is a simple array of slot indices (e.g., `[0, 2]`), which does not match the OpenBambuAPI specification.
 
 According to the OpenBambuAPI spec, `ams_mapping` must be a 5-element array where each position corresponds to a filament color slot in the print file. Unused positions must be padded with `-1`. For example, a print using only AMS slot 0 sends `[-1, -1, -1, -1, 0]`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bambu-printer-mcp",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "MCP server for Bambu Lab 3D printers with STL manipulation, slicing, and print management",
   "main": "dist/index.js",
   "repository": "https://github.com/DMontgomery40/bambu-printer-mcp",