bambu-printer-mcp

Overview Schema Source Related Servers Discussions Admin

print_3mf

Print a 3MF file on a Bambu Lab printer, auto-slicing when no G-code is embedded. Specify the printer model to ensure safe operation.

Instructions

Print a 3MF file on a Bambu Lab printer. Auto-slices if the 3MF has no gcode. IMPORTANT: bambu_model must be specified to ensure safe printer operation.

Input Schema

Name	Required	Description
`host`	No	Hostname or IP of the printer (default: value from env)
`dev_id`	No	Bambu device id for FULU BambuNetwork printing; defaults to BAMBU_DEV_ID or BAMBU_SERIAL.
`dev_ip`	No	Printer IP address for FULU BambuNetwork LAN/local print methods; defaults to host when provided.
`use_ams`	No	Whether to use the AMS (default: auto-detect from 3MF)
`bed_type`	No	Bed plate type currently installed (default: textured_plate)
`ams_slots`	No	Preferred AMS input: one absolute tray index per USED filament in plate order, e.g. [1] for a single-filament print pulling from AMS 0 slot 1. Use 254 for the external spool (on dual-nozzle printers: 254 = left/deputy nozzle external, 255 = right/main nozzle external). Expanded to project-level ams_mapping automatically from the 3MF's plate_N.json and gcode header.
`timelapse`	No	Enable timelapse recording (default: false)
`user_info`	No	Optional BambuNetwork user_info JSON string passed to net.change_user for the FULU bridge.
`ams_mapping`	No	Project-level AMS mapping array. Position = project filament index, value = absolute AMS tray (0-3=AMS 0, 4-7=AMS 1, 8-11=AMS 2, 128+=AMS-HT, 254=external, -1=unused). On dual-nozzle printers (H2D, H2D Pro, H2C, X2D) 254 is the LEFT/deputy nozzle external spool and 255 the RIGHT/main nozzle external spool, matching Bambu Studio's virtual tray ids; the gcode header's filament_map (1=left, 2=right) says which nozzle each filament was sliced for. Prefer ams_slots unless you know the project-level layout.
`bambu_model`	Yes	REQUIRED: Bambu Lab printer model. Ask the user if not known. Using the wrong model can damage the printer.
`bambu_token`	No	Access token (default: value from env)
`nozzle_type`	No	Installed nozzle material, used when the 3MF must be auto-sliced (default: BAMBU_NOZZLE_TYPE, else the preset's stock nozzle).
`plate_index`	No	Zero-based plate index to print from the sliced 3MF (default: 0)
`slicer_path`	No	Path to the slicer executable for auto-slicing (default: value from env or a platform default). Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1.
`slicer_type`	No	Slicer to use only if auto-slicing an unsliced 3MF. Bambu-compatible slicer aliases such as fulu-orca and orca-studio are accepted.
`bambu_serial`	No	Serial number (default: value from env)
`bed_leveling`	No	Enable auto bed leveling (default: true)
`country_code`	No	BambuNetwork country code, such as US, used by the FULU bridge agent.
`template_dir`	No	Optional template directory override when resolving template_name.
`template_name`	No	Optional named template from the local registry. Resolves to template_3mf_path automatically.
`three_mf_path`	Yes	Path to the 3MF file to print
`auto_match_ams`	No	When true, match the sliced 3MF's tray_info_idx requirements against live AMS inventory and use the resulting ams_slots. Ignored when ams_mapping or ams_slots is provided.
`bridge_command`	No	Override command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1.
`slicer_profile`	No	Path to the slicer profile/config file for auto-slicing (optional).
`try_emmc_print`	No	X2D native printing: true stores the job on internal storage (eMMC), false on the SD card or USB stick (refused unless the printer reports one ready). Omit to use the card when ready, else eMMC; BAMBU_NATIVE_TRY_EMMC_PRINT sets a server default.
`connection_mode`	No	Print path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in, storing the job on a ready SD card or USB stick, otherwise internal eMMC); lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge.
`connection_type`	No	BambuNetwork connection type when connection_mode is bambu_network; cloud uses restored internet printing, lan uses local bridge printing.
`nozzle_diameter`	No	Nozzle diameter in mm for auto-slicing (default: 0.4)
`flow_calibration`	No	Enable flow calibration (default: true)
`nozzle_diameters`	No	Complete per-nozzle diameters for a pre-sliced job, e.g. [0.4, 0.6]. Omit to verify its declared diameters against live telemetry; cannot combine with nozzle_diameter.
`template_3mf_path`	No	Optional template 3MF whose embedded Bambu slicer settings should be reused when auto-slicing this print job.
`nozzle_volume_type`	No	Installed nozzle flow type, used when the 3MF must be auto-sliced (default: BAMBU_NOZZLE_VOLUME_TYPE, else standard).
`bambu_network_method`	No	FULU print method when connection_mode is bambu_network; defaults to start_print for cloud and start_local_print for lan.
`vibration_calibration`	No	Enable vibration calibration (default: true)
`bambu_network_config_dir`	No	Config/log directory used by the FULU BambuNetwork agent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.32Oct 23, 2026

changedInput schema / properties / connection_mode / description

Previous value: -"Print path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in and emmc tunnel); lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge."New value: +"Print path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in, storing the job on a ready SD card or USB stick, otherwise internal eMMC); lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge."

addedInput schema / properties / try_emmc_print

Added value: +{
+  "description": "X2D native printing: true stores the job on internal storage (eMMC), false on the SD card or USB stick (refused unless the printer reports one ready). Omit to use the card when ready, else eMMC; BAMBU_NATIVE_TRY_EMMC_PRINT sets a server default.",
+  "type": "boolean"
+}

Changed4 schema fields changedv1.1.31Oct 19, 2026

changedInput schema / properties / ams_mapping / description

Previous value: -"Project-level AMS mapping array. Position = project filament index, value = absolute AMS tray (0-3=AMS 0, 4-7=AMS 1, 8-11=AMS 2, 128+=AMS-HT, 254=external, -1=unused). Prefer ams_slots unless you know the project-level layout."New value: +"Project-level AMS mapping array. Position = project filament index, value = absolute AMS tray (0-3=AMS 0, 4-7=AMS 1, 8-11=AMS 2, 128+=AMS-HT, 254=external, -1=unused). On dual-nozzle printers (H2D, H2D Pro, H2C, X2D) 254 is the LEFT/deputy nozzle external spool and 255 the RIGHT/main nozzle external spool, matching Bambu Studio's virtual tray ids; the gcode header's filament_map (1=left, 2=right) says which nozzle each filament was sliced for. Prefer ams_slots unless you know the project-level layout."

changedInput schema / properties / ams_slots / description

Previous value: -"Preferred AMS input: one absolute tray index per USED filament in plate order, e.g. [1] for a single-filament print pulling from AMS 0 slot 1. Expanded to project-level ams_mapping automatically from the 3MF's plate_N.json and gcode header."New value: +"Preferred AMS input: one absolute tray index per USED filament in plate order, e.g. [1] for a single-filament print pulling from AMS 0 slot 1. Use 254 for the external spool (on dual-nozzle printers: 254 = left/deputy nozzle external, 255 = right/main nozzle external). Expanded to project-level ams_mapping automatically from the 3MF's plate_N.json and gcode header."

addedInput schema / properties / nozzle_volume_type

Added value: +{
+  "description": "Installed nozzle flow type, used when the 3MF must be auto-sliced (default: BAMBU_NOZZLE_VOLUME_TYPE, else standard).",
+  "enum": [
+    "standard",
+    "high_flow"
+  ],
+  "type": "string"
+}

changedInput schema / properties / slicer_type / enum

Previous value: -[
-  "bambustudio",
-  "orcaslicer",
-  "orcaslicer-bambulab",
-  "prusaslicer",
-  "cura",
-  "slic3r",
-  "fulu-orca",
-  "fulu-orcaslicer",
-  "orca-studio",
-  "orca-bambulab"
-]New value: +[
+  "bambustudio",
+  "orcaslicer",
+  "orcaslicer-bambulab",
+  "orca-slicer-api",
+  "prusaslicer",
+  "cura",
+  "slic3r",
+  "fulu-orca",
+  "fulu-orcaslicer",
+  "orca-studio",
+  "orca-bambulab"
+]

Changed1 schema field changedv1.1.22Oct 1, 2026

addedInput schema / properties / nozzle_type

Added value: +{
+  "description": "Installed nozzle material, used when the 3MF must be auto-sliced (default: BAMBU_NOZZLE_TYPE, else the preset's stock nozzle).",
+  "enum": [
+    "stainless_steel",
+    "hardened_steel",
+    "tungsten_carbide",
+    "brass"
+  ],
+  "type": "string"
+}

Changed6 schema fields changedv1.1.14Sep 29, 2026

changedInput schema / properties / bambu_model / enum

Previous value: -[
-  "p1s",
-  "p1p",
-  "p2s",
-  "x1c",
-  "x1e",
-  "a1",
-  "a1mini",
-  "h2d",
-  "h2s"
-]New value: +[
+  "p1s",
+  "p1p",
+  "p2s",
+  "x1c",
+  "x1e",
+  "a1",
+  "a1mini",
+  "h2d",
+  "h2s",
+  "h2c",
+  "x2d"
+]

changedInput schema / properties / bridge_command / description

Previous value: -"Override command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND."New value: +"Override command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1."

changedInput schema / properties / connection_mode / description

Previous value: -"Print path to use: lan_mqtt_ftps uses this MCP's direct local MQTT/FTPS path; bambu_network uses the restored FULU BambuNetwork bridge."New value: +"Print path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in and emmc tunnel); lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge."

changedInput schema / properties / connection_mode / enum

Previous value: -[
-  "lan_mqtt_ftps",
-  "bambu_network"
-]New value: +[
+  "lan_mqtt_ftps",
+  "bambu_network",
+  "bambu_native",
+  "bambu_connect"
+]

addedInput schema / properties / nozzle_diameters

Added value: +{
+  "description": "Complete per-nozzle diameters for a pre-sliced job, e.g. [0.4, 0.6]. Omit to verify its declared diameters against live telemetry; cannot combine with nozzle_diameter.",
+  "items": {
+    "enum": [
+      0.2,
+      0.4,
+      0.6,
+      0.8
+    ],
+    "type": "number"
+  },
+  "maxItems": 2,
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / properties / slicer_path / description

Previous value: -"Path to the slicer executable for auto-slicing (default: value from env or a platform default)"New value: +"Path to the slicer executable for auto-slicing (default: value from env or a platform default). Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1."

First observedv1.1.1May 17, 2026

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It does disclose two useful traits: automatic slicing for gcode-less 3MFs and that bambu_model must be specified for safe operation. It says nothing about the physical irreversibility of starting a print, credential/token requirements, or which connection path is used by default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and the auto-slice trait, then the safety warning. No filler. Slightly penalized only because the 'IMPORTANT' clause duplicates a schema field description rather than adding new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a high-complexity, 35-parameter, print-triggering tool with no annotations and no output schema. The schema is rich enough that parameter-level gaps are mostly covered, but the description does not convey the default print path, what the caller should expect on submission, or how the FULU/bambu_network variants relate to this call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the per-parameter descriptions (ams_slots, ams_mapping, connection_mode, try_emmc_print) are extensive, so the baseline is 3. The description adds no parameter meaning beyond repeating the schema's own warning that bambu_model is required, so it does not exceed the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Print a 3MF file on a Bambu Lab printer') and adds a distinctive behavior ('Auto-slices if the 3MF has no gcode'). However, it does not distinguish itself from close siblings like print_3mf_bambu_network, start_print, or start_print_job, so an agent cannot tell from the description alone which entry point to choose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Only implied usage: the tool is for 3MF files. There is no explicit guidance on when to use this versus print_3mf_bambu_network, start_print, or start_print_job, and the 35-parameter surface (connection_mode alone offers four paths) makes that routing question very real for a caller.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

print_3mf

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools