Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

slice_stl

Slices STL or 3MF files into printable G-code or sliced 3MF for Bambu Lab printers, requiring the correct printer model to generate safe output.

Instructions

Slice an STL or 3MF file using a slicer to generate printable G-code or sliced 3MF. IMPORTANT: bambu_model must be specified to ensure the slicer generates safe G-code for the correct printer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNoUniform scale factor applied to all axes. 1.0 = original size, 2.0 = double, 0.5 = half. Applied before slicing.
orientNoAuto-orient the model for optimal printability (minimize supports, maximize bed adhesion). Recommended for raw STL imports that lack a pre-set orientation.
rotateNoRotate the model around the Z-axis (vertical) by this many degrees before slicing. Positive = counterclockwise when viewed from above.
arrangeNoAuto-arrange all objects on the build plate with optimal spacing. Recommended when importing STLs or adding multiple objects. Set false to preserve existing plate layout.
bed_typeNoBed plate type for slicing (default: textured_plate). SuperTack is accepted only for pre-sliced print jobs until the BambuStudio CLI identifier is verified.
min_saveNoWrite a smaller output 3MF by omitting non-essential metadata. Reduces file size for faster FTP upload to the printer.
rotate_xNoRotate the model around the X-axis by this many degrees before slicing. Useful for reorienting prints for better layer adhesion.
rotate_yNoRotate the model around the Y-axis by this many degrees before slicing. Useful for reorienting prints for better layer adhesion.
stl_pathYesPath to the STL or 3MF file to slice
uptodateNoRefresh 3MF preset configs to match the latest BambuStudio version. Use when slicing downloaded or older 3MF files to prevent stale-config failures.
bambu_modelYesREQUIRED: Bambu Lab printer model. Ask the user if not known. Using the wrong model can damage the printer.
nozzle_typeNoBambu-compatible slicing: the hotend nozzle material installed on the printer (default: BAMBU_NOZZLE_TYPE, else the model preset's stock nozzle, usually stainless_steel). Printing compares it with the printer's reported nozzle.
repetitionsNoPrint N identical copies of the model. Each copy gets its own plate placement. Example: 3 prints three copies.
slice_plateNoWhich plate index to slice. 0 = all plates (default). Use 1, 2, etc. to slice only a specific plate in multi-plate 3MF projects.
slicer_pathNoPath to the slicer executable (default: value from env). Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1.
slicer_typeNoType of slicer to use. Bambu-compatible choices (bambustudio, orcaslicer, orcaslicer-bambulab) export sliced 3MF; aliases such as fulu-orca and orca-studio are accepted.
skip_objectsNoSkip specific objects during slicing by index. Comma-separated, e.g. '3,5,10'. Useful for multi-object 3MFs where you only want to print some parts.
template_dirNoOptional template directory override when resolving template_name.
clone_objectsNoDuplicate specific objects on the plate. Comma-separated clone counts per object index, e.g. '1,3,1,10' clones object 0 once, object 1 three times, etc.
ensure_on_bedNoDetect models floating above the bed and lower them onto the build surface. Safety net for imported models with incorrect Z origins.
template_nameNoOptional named template from the local registry. Resolves to template_3mf_path automatically.
allow_mix_tempNoAllow filaments with different temperature requirements on the same plate. Required for multi-material prints mixing e.g. PLA and PETG.
load_filamentsNoOverride filament profiles. Semicolon-separated paths to filament JSON configs, e.g. 'pla_basic.json;petg_cf.json'.
slicer_profileNoPath to an optional process profile/config file. The exact bambu_model/nozzle machine preset is still required.
nozzle_diameterNoNozzle diameter in mm (default: 0.4)
enable_timelapseNoInsert timelapse parking moves into gcode. The toolhead parks at a fixed position each layer for camera capture. Adds ~10% print time.
filament_coloursNoOptional slot colours, one #RRGGBB per filament slot in order, separated by ';' (e.g. '#161616;#FFFFFF'). Defaults to the input 3MF's project colours, else the BambuStudio default.
filament_profileNoCompatibility alias for load_filaments. Semicolon-separated Orca/Bambu filament profile JSON paths.
load_filament_idsNoMap filaments to objects/parts. Comma-separated IDs matching load_filaments order, e.g. '1,2,3,1' assigns filament 1 to objects 0 and 3.
template_3mf_pathNoOptional template 3MF whose embedded Bambu slicer settings should be reused when slicing a new STL or 3MF.
skip_modified_gcodesNoStrip custom start/end gcodes embedded in the 3MF. Recommended for downloaded 3MFs since custom gcodes from other users' profiles may be unsafe for your printer.
use_printer_filamentsNoWhen true, and no explicit slicer profile or load_filaments override is provided, use the printer's current or first loaded AMS filament as the slicer filament profile. Template 3MF process settings can still be used at the same time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.22
    • addedInput schema / properties / nozzle_type
      Added value: +{
+  "description": "Bambu-compatible slicing: the hotend nozzle material installed on the printer (default: BAMBU_NOZZLE_TYPE, else the model preset's stock nozzle, usually stainless_steel). Printing compares it with the printer's reported nozzle.",
+  "enum": [
+    "stainless_steel",
+    "hardened_steel",
+    "tungsten_carbide",
+    "brass"
+  ],
+  "type": "string"
+}
  2. Changed4 schema fields changedv1.1.14
    • 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"
+]
    • addedInput schema / properties / filament_colours
      Added value: +{
+  "description": "Optional slot colours, one #RRGGBB per filament slot in order, separated by ';' (e.g. '#161616;#FFFFFF'). Defaults to the input 3MF's project colours, else the BambuStudio default.",
+  "type": "string"
+}
    • changedInput schema / properties / slicer_path / description
      Previous value: -"Path to the slicer executable (default: value from env)"New value: +"Path to the slicer executable (default: value from env). Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1."
    • changedInput schema / properties / slicer_profile / description
      Previous value: -"Path to the slicer profile/config file (optional, overrides bambu_model preset)"New value: +"Path to an optional process profile/config file. The exact bambu_model/nozzle machine preset is still required."
  3. First observedv1.1.1

TDQS

A3.5/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 behavioral burden. It usefully flags the safety-critical requirement and the risk of damaging the printer with the wrong model, but it says nothing about the output artifact (where the G-code/3MF is written, what path is returned) or side effects, which matters for a tool whose whole job is producing a file.

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?

Two sentences, zero waste, and the critical requirement is front-loaded with an IMPORTANT marker. It is tight and well-structured, though for a 32-parameter tool the extreme brevity leaves useful information unstated.

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?

This is a highly complex tool (32 params, 4 enums, no output schema, no annotations). The description never states what the call returns or where the sliced output lands, nor does it cover the interaction with sibling tools like upload_gcode. For this complexity level, the definition is too thin.

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% across all 32 parameters, so the schema already documents every parameter, including the bambu_model warning the description repeats. The description adds no parameter meaning beyond the schema, which sets the baseline at 3.

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?

States a specific verb+resource (slice an STL or 3MF) and the outcome (printable G-code or sliced 3MF). This clearly distinguishes it from siblings like scale_stl, rotate_stl, and slice_with_template, which share the domain but do different things.

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 gives a hard prerequisite (bambu_model must be specified) and explains why (safe G-code for the correct printer), which is real usage context. However, it never routes the agent against alternatives such as slice_with_template or get_slice_settings, so the when-to-use-this-vs-another guidance is only implied.

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

Deploy Server

Other Tools