bambu-printer-mcp

Overview Schema Source Related Servers Discussions Admin

print_3mf_bambu_network

Print a 3MF file through the restored BambuNetwork path instead of MCP LAN MQTT/FTPS, enabling cloud or local bridge printing with Bambu printer settings.

Instructions

Print a 3MF through FULU OrcaSlicer-bambulab's restored BambuNetwork path instead of the MCP LAN MQTT/FTPS path.

Input Schema

Name	Required	Description
`host`	No	Printer host or IP address, used as dev_ip for LAN/local bridge methods.
`dev_id`	No	Bambu device id used by BambuNetwork; defaults to BAMBU_DEV_ID or BAMBU_SERIAL.
`dev_ip`	No	Printer IP address for LAN/local bridge methods; defaults to host when provided.
`use_ams`	No	Whether to use the AMS; defaults to auto-detect from the 3MF mapping.
`bed_type`	No	Bed plate type currently installed (default: textured_plate).
`password`	No	Printer password/access code override for LAN/local bridge methods.
`username`	No	Printer username for LAN/local bridge methods; defaults to bblp.
`ams_slots`	No	Per-used-filament AMS slot list, matching the local LAN print path (254/255 external spool rules as in print_3mf).
`task_name`	No	Optional project label when project_name is omitted. The submitted task name uses a unique inspected-job identity for safe resume.
`timelapse`	No	Enable timelapse recording in FULU PrintParams (default: false).
`user_info`	No	Optional BambuNetwork user_info JSON string to pass to net.change_user after the agent starts.
`timeout_ms`	No	Bridge request timeout in milliseconds.
`ams_mapping`	No	AMS slot mapping array used by both local MCP printing and FULU PrintParams. Same tray values as print_3mf: 254 = external spool; on dual-nozzle printers 254 = left/deputy nozzle external and 255 = right/main nozzle external.
`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	Printer access code/password for LAN/local bridge methods.
`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; converted to FULU's one-based PrintParams plate_index.
`preset_name`	No	Optional preset name sent in FULU PrintParams; defaults to project plus one-based plate index.
`slicer_path`	No	Path to the slicer executable for auto-slicing; defaults to 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; use orcaslicer-bambulab for FULU's fork.
`ams_mapping2`	No	Raw JSON string for FULU PrintParams ams_mapping2, matching OrcaSlicer-bambulab's v1 AMS mapping field.
`bambu_serial`	No	Fallback Bambu device id when dev_id is not supplied.
`bed_leveling`	No	Enable auto bed leveling in FULU PrintParams (default: true).
`country_code`	No	BambuNetwork country code, such as US, used by the agent during startup.
`nozzles_info`	No	Raw JSON string for FULU PrintParams nozzles_info.
`project_name`	No	Optional project name sent in FULU PrintParams; defaults to the 3MF filename without extension.
`client_job_id`	No	Optional client job id sent to the bridge; defaults to the current timestamp.
`extra_options`	No	Raw JSON string or text for FULU PrintParams extra_options.
`layer_inspect`	No	Enable first-layer inspection where supported (default: false for BambuNetwork bridge).
`three_mf_path`	Yes	Path to the 3MF file to print; unsliced 3MFs are auto-sliced before sending.
`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.
`nozzle_mapping`	No	Raw JSON string for FULU PrintParams nozzle_mapping.
`slicer_profile`	No	Path to an optional slicer profile/config file for auto-slicing.
`try_emmc_print`	No	Store the job on internal storage (eMMC) instead of the SD card or USB stick. FULU bridge: default false. X2D native printing: omit to use a ready card, else eMMC.
`config_filename`	No	Optional config 3MF path for cloud print; defaults to the same 3MF path.
`connection_type`	No	BambuNetwork connection type to put in FULU PrintParams; cloud uses restored internet printing, lan uses local bridge printing.
`nozzle_diameter`	No	Nozzle diameter in mm for auto-slicing (default: 0.4).
`use_ssl_for_ftp`	No	Whether FULU local print should use SSL for FTP (default: true).
`ams_mapping_info`	No	Raw JSON string for FULU PrintParams ams_mapping_info, matching OrcaSlicer-bambulab's detailed AMS mapping field.
`flow_calibration`	No	Enable flow calibration in FULU PrintParams (default: true).
`nozzle_diameters`	No	Complete per-nozzle diameters for pre-sliced jobs, e.g. [0.4, 0.6]. Omit to verify file metadata against every reported nozzle; cannot combine with nozzle_diameter.
`use_ssl_for_mqtt`	No	Whether FULU local print should use SSL for MQTT (default: true).
`ams_mapping_bridge`	No	Raw JSON string override for FULU PrintParams ams_mapping when the automatic array is not enough.
`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 to invoke; defaults to start_print for cloud and start_local_print for lan.
`vibration_calibration`	No	Enable vibration calibration in FULU PrintParams (default: true).
`external_change_assist`	No	Enable FULU PrintParams task_ext_change_assist for external filament change assistance.
`bambu_network_config_dir`	No	Config/log directory used by the BambuNetwork agent; defaults to BAMBU_NETWORK_CONFIG_DIR or a user config directory.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.32Oct 23, 2026

changedInput schema / properties / try_emmc_print / description

Previous value: -"Enable FULU PrintParams try_emmc_print for printers that support internal storage printing."New value: +"Store the job on internal storage (eMMC) instead of the SD card or USB stick. FULU bridge: default false. X2D native printing: omit to use a ready card, else eMMC."

Changed4 schema fields changedv1.1.31Oct 19, 2026

changedInput schema / properties / ams_mapping / description

Previous value: -"AMS slot mapping array used by both local MCP printing and FULU PrintParams."New value: +"AMS slot mapping array used by both local MCP printing and FULU PrintParams. Same tray values as print_3mf: 254 = external spool; on dual-nozzle printers 254 = left/deputy nozzle external and 255 = right/main nozzle external."

changedInput schema / properties / ams_slots / description

Previous value: -"Per-used-filament AMS slot list, matching the local LAN print path."New value: +"Per-used-filament AMS slot list, matching the local LAN print path (254/255 external spool rules as in print_3mf)."

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"
+}

Changed5 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."

addedInput schema / properties / nozzle_diameters

Added value: +{
+  "description": "Complete per-nozzle diameters for pre-sliced jobs, e.g. [0.4, 0.6]. Omit to verify file metadata against every reported nozzle; 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; defaults to value from env or a platform default."New value: +"Path to the slicer executable for auto-slicing; defaults to value from env or a platform default. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1."

changedInput schema / properties / task_name / description

Previous value: -"Optional BambuNetwork task name; defaults to the project name."New value: +"Optional project label when project_name is omitted. The submitted task name uses a unique inspected-job identity for safe resume."

First observedv1.1.1May 17, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It adds the transport-path distinction, but it does not disclose that this is a physical/ irreversible printer command, what credentials or bridge requirements are needed, or what happens on failure.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no filler. It states the action and the path distinction immediately.

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

Completeness2/5

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

For a 48-parameter physical-print tool with no annotations and no output schema, one sentence is not enough. It omits when to prefer this over print_3mf/start_print, bridge/auth prerequisites, and the physical side effects that matter for safe invocation.

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%, so the schema already documents all 48 parameters. The description adds no parameter-level meaning beyond the schema; baseline 3 is appropriate.

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

Purpose5/5

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

The description gives a specific verb and resource ("Print a 3MF") and explicitly distinguishes the transport path from the MCP LAN MQTT/FTPS alternative. An agent can tell this is the BambuNetwork-path print tool rather than the general print_3mf path.

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

Usage Guidelines3/5

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

It implies when to use the tool by saying it prints through the BambuNetwork path "instead of the MCP LAN MQTT/FTPS path," but it does not state a concrete condition for choosing this tool over print_3mf/start_print, nor does it name the sibling alternatives explicitly.

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

print_3mf_bambu_network

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools