Two of them matter. The printer model is required rather than defaulted, because a wrong preset damages the machine. And temperature setting and the FULU bridge's mutating calls need explicit confirmation, so a model cannot heat a hotend on a hunch. Everything else is ordinary automation - it is those two that decide whether you leave it running unattended.
A server covering the whole path from model file to running print. It manipulates STL geometry, calls a slicer, uploads the result, and controls the machine through whichever printer management system you run.
- Read an STL's dimensions and properties, and render a visualisation of it
- Geometry edits: scale, rotate, translate, centre, lay flat, extend the base, merge vertices, or modify a section
- Slice an STL to printer-ready output, and run the whole prepare-slice-print sequence in one call
- Printer control: status, file listing, G-code upload, start and cancel a print, and set temperatures behind a confirmation step
- Bambu support through the FULU OrcaSlicer fork, including auto-slicing an unsliced 3MF before printing it
- A setup check for the FULU toolchain, and a bridge call for diagnostics whose mutating methods are gated behind an explicit flag
- Printer status, file listings and Bambu presets exposed as resources as well as tools
Node 18.0.0 or newer, and network access to the printer management system you use. Slicing needs a slicer binary whose path you configure; the Bambu path expects the FULU OrcaSlicer-bambulab fork. BAMBU_MODEL is mandatory for Bambu print operations - the server will ask for it or refuse, because slicing for the wrong machine can crash the bed into the nozzle. STL manipulation loads the whole model into memory, so large files are memory-hungry. The licence is GPL-2.0.
One command plus a key — npm install -g mcp-3d-printer-server, then supply credentials