Labsco
DMontgomery40 logo

MCP 3D Printer Server

★ 196

from DMontgomery40

Connects to 3D printer management systems like OctoPrint, Klipper, and Bambu Labs for model manipulation and printing workflows.

🔥🔥🔥✓ VerifiedPaid serviceAdvanced setup
#automation#cloud#devops#git#search#maps#security#translation

Thank You To FULU And Louis Rossmann

Thank you to the FULU Foundation and Louis Rossmann for standing up for consumer ownership, open source developers, repair rights, and users who should not have working hardware made worse by locked-down software. This MCP server treats the FULU OrcaSlicer-bambulab fork as a first-class Bambu project slicer target.

MCP 3D Printer Server

✨ What's New / Significant Updates (as of last session)

  • Dual Local Transports: Added explicit stdio and streamable-http runtime modes with environment-based transport selection.

  • FULU OrcaSlicer-bambulab Support: Added orcaslicer-bambulab / fulu_orca slicer support for Bambu project 3MF export, and made it the default Bambu slicer target when no slicer is configured.

  • Bambu Reliability Pass: Fixed Bambu argument wiring bugs, added FTP-backed file operations, improved status refresh behavior, and implemented practical command paths for startJob, setTemperature, and print_3mf.

  • Blender Bridge Tooling: Added blender_mcp_edit_model with optional execution mode for model-edit collaboration workflows.

  • Transport Behavior Tests: Added real behavior tests for both transports (initialize, tools/list, success + failing tools/call, origin rejection).

  • Docker Modernization: Updated Docker build flow to work without BuildKit-specific features and verified streamable HTTP initialization in container smoke testing.

🗺️ Roadmap / TODO

  • Achieve Feature Parity: Bring functionality (status detail, file operations, direct printing where possible, preset handling) for OctoPrint, Klipper, Duet, Repetier, Prusa Connect, and Creality Cloud up to the level of robustness planned for the Bambu implementation.

  • Implement Full Bambu MQTT Status: Refactor getStatus for Bambu to subscribe to MQTT reports and maintain real-time state.

  • Implement Robust AMS Mapping: Replace placeholder logic; correctly parse and use AMS mapping from .3mf slicer config or user overrides for the MQTT print command.

  • Implement .3mf Print Overrides: Add logic to the print_3mf tool to handle user-provided overrides (e.g., calibration flags) and potentially common slicer settings if feasible via MQTT/G-code.

  • Calculate MD5 Hash: Add logic to calculate and include the MD5 hash of the .3mf file in the MQTT print command (optional but recommended by protocol).

  • Refactor Bambu File Ops: Investigate replacing bambu-js FTP operations (getFiles, uploadFile) with direct MQTT methods if possible/stable, or contribute FTPS support to bambu-js.

  • Add Preset Discovery Logic: Improve preset resource listing (currently lists based on potential filenames, could parse index files if they exist).

  • Expand .3mf Support: Add .3mf printing support for other printer types where applicable.

  • Error Handling & Reporting: Enhance MQTT error handling and reporting of print progress/completion.

  • Testing: Conduct thorough runtime testing of all new Bambu features.

Click to expand Table of Contents

Table of Contents

  • Description

  • Features

  • Installation

  • Prerequisites

  • Install from npm

  • Install from source

  • Running with Docker

  • Using Slicers with Docker

  • Configuration

  • Usage

  • Supported Printer Management Systems

  • OctoPrint

  • Klipper (via Moonraker)

  • Duet

  • Repetier

  • Bambu Labs

  • Finding Your Bambu Printer's Serial Number and Access Token

  • Bambu Communication Notes (MQTT & FTP)

  • Prusa Connect

  • Setting up Prusa Connect

  • Creality Cloud

  • Setting up Creality Cloud

  • Available Tools

  • STL Manipulation Tools

  • Printer Control Tools

  • Bambu-Specific Tools

  • Available Resources

  • Printer Resources

  • Bambu Preset Resources

  • Example Commands for LLM

  • Bambu Lab Printer Limitations

  • Limitations and Considerations

  • Memory Usage

  • STL Manipulation Limitations

  • Visualization Limitations

  • Performance Considerations

  • Testing Recommendations

  • Appendix: MCP Safety Notes

  • Badges

  • License

Description

This is a server that allows MCP users to connect with the API endpoints of these 3D Printers:

  • OctoPrint

  • Klipper (Moonraker)

  • Duet

  • Repetier

  • Bambu Labs

  • Prusa Connect

  • Creality/Ender

This server is a Model Context Protocol (MCP) server for connecting Claude with 3D printer management systems. It allows MCP to interact with 3D printers through the APIs of various printer management systems such as OctoPrint, Klipper (via Moonraker), Duet, Repetier, and Bambu Labs printers.

Note on Resource Usage: This MCP server includes advanced 3D model manipulation features that can be memory-intensive when working with large STL files. Please see the "Limitations and Considerations" section for important information about memory usage and performance.

Features

  • Get printer status (temperatures, print progress, etc.)

  • List files on the printer

  • Upload G-code files to the printer

  • Start, cancel, and monitor print jobs

  • Set printer temperatures

  • Advanced STL file manipulation:

  • Extend base for better adhesion

  • Scale models uniformly or along specific axes

  • Rotate models around any axis

  • Translate (move) models

  • Modify specific sections of STL files (top, bottom, center, or custom)

  • Comprehensive STL analysis with detailed model information

  • Generate multi-angle SVG visualizations of STL files

  • Real-time progress reporting for long operations

  • Error handling with detailed diagnostics

  • Slice STL files to generate G-code

  • Confirm temperature settings in G-code files

  • Complete end-to-end workflow from STL modification to printing

  • Print .3mf files directly on Bambu Lab printers (via MQTT command)

  • Slice Bambu projects with FULU OrcaSlicer-bambulab (SLICER_TYPE=orcaslicer-bambulab) and auto-slice unsliced 3MF files before Bambu printing when a project slicer is configured

  • Inspect and probe the FULU BambuNetwork runtime (check_fulu_orca_setup) and call safe-by-default FULU bridge RPC methods for diagnostics and development (fulu_bambu_network_rpc)

  • Read Bambu Studio preset files (printer, filament, process) as resources

Supported Printer Management Systems

OctoPrint

OctoPrint is a popular web interface for 3D printers. It provides a REST API for controlling the printer.

  • Default port: 80 (http) or 443 (https)

  • Authentication: API key required

Klipper (via Moonraker)

Klipper is a firmware for 3D printers that works with the Moonraker API server.

  • Default port: 7125

  • Authentication: Depends on your Moonraker configuration

Duet

Duet is a control board for 3D printers with its own web interface (DuetWebControl).

  • Default port: 80 (http) or 443 (https)

  • Authentication: Depends on your Duet configuration

Repetier

Repetier-Server is a host software for 3D printers.

  • Default port: 3344

  • Authentication: API key required

Bambu Labs

Bambu Lab printers use MQTT for status and control and FTP for file operations.

  • Authentication: Serial number and access token required (set BAMBU_SERIAL and BAMBU_TOKEN)

  • Printer model: Required (set BAMBU_MODEL). Valid values: p1s, p1p, x1c, x1e, a1, a1mini, h2d. This ensures the slicer generates correct G-code for your specific printer.

  • Requirements: Printer must be on the same network with Developer Mode and LAN Only Mode enabled

  • Compatible with: X1C, X1E, P1S, P1P, A1, A1 Mini, H2D

Finding Your Bambu Printer's Serial Number and Access Token

To connect to your Bambu Lab printer, you need two things:

Printer Serial Number:

  • Look on the back or bottom of your printer for a sticker with a serial number (typically starts with "01P" or "01A" followed by numbers/letters)

  • Alternatively, open Bambu Studio, connect to your printer, go to Device > Device Management, and view your printer's information

Access Token:

  • The access token is a security code needed to connect directly to your printer

  • For P1 Series printers: Go to the touchscreen, select Settings > Network > LAN Mode, and you'll see the access code

  • For X1 Series printers: Go to the touchscreen, select Settings > Network > LAN Mode, and enable LAN Mode to see the access code

  • For A1 Mini: Use the Bambu Handy app to connect to your printer, then go to Settings > Network > LAN Mode

Note: If your printer is not on the same local network or you can't find the access token, you may need to update your printer's firmware to the latest version to enable LAN Mode.

Bambu Communication Notes (MQTT & FTP)

  • MQTT: This server uses the local MQTT protocol (port 8883, TLS) based on community findings (e.g., OpenBambuAPI) to send commands like starting prints and cancelling jobs.

  • FTP: File listing and uploading currently rely on the FTP server running on the printer (via the bambu-js library helper). Note: This FTP connection might be unsecured (plain FTP) based on current library limitations. Use with awareness of your network security.

Prusa Connect

Prusa Connect is Prusa's own cloud-based solution for managing their printers.

  • Default port: 80 (http) or 443 (https)

  • Authentication: API key required

  • Compatible with: Prusa MK4, Prusa Mini, Prusa XL, and other Prusa printers with Prusa Connect

For Prusa Connect cloud, use connect.prusa3d.com with PRINTER_PORT=443, or include the scheme directly with PRINTER_HOST=https://connect.prusa3d.com. The server normalizes both forms to HTTPS. Local PrusaLink hosts continue to use HTTP unless you provide an https:// host or port 443.

Setting up Prusa Connect

  • Make sure your Prusa printer is updated to the latest firmware

  • Connect your printer to your Wi-Fi network

  • Create a Prusa Connect account and register your printer

  • Generate an API key from the Prusa Connect web interface under Settings > API Access

Creality Cloud

Creality Cloud is Creality's management system for their printers.

  • Default port: 80 (http) or 443 (https)

  • Authentication: Bearer token required

  • Compatible with: Ender series, CR series, and other Creality printers with network capabilities

Setting up Creality Cloud

  • Install the Creality Cloud app on your mobile device

  • Create an account and add your printer

  • Enable local network access for your printer

  • Generate a token from the Creality Cloud app under Settings > Developer Options

Available Tools

Click to expand STL Manipulation Tools

STL Manipulation Tools

Memory Usage Warning: The following STL manipulation tools load entire 3D models into memory. For large or complex STL files (>10MB), these operations can consume significant memory. When using these tools within the MCP environment, be mindful of memory constraints.

get_stl_info

Get detailed information about an STL file, including dimensions, vertex count, and bounding box.

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl"
}

extend_stl_base

Extend the base of an STL file by a specified amount.

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "extension_inches": 2
}

scale_stl

Scale an STL model uniformly or along specific axes.

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "scale_factor": 1.5
}

Or for non-uniform scaling:

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "scale_x": 1.2,
 "scale_y": 1.0,
 "scale_z": 1.5
}

rotate_stl

Rotate an STL model around specific axes (in degrees).

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "rotate_x": 45,
 "rotate_y": 0,
 "rotate_z": 90
}

translate_stl

Move an STL model along specific axes (in millimeters).

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "translate_x": 10,
 "translate_y": 5,
 "translate_z": 0
}

merge_vertices

Merge vertices that are closer than a specified tolerance. Helps close small gaps and can slightly simplify the mesh.

Copy & paste — that's it
{
 "stl_path": "/path/to/model.stl",
 "tolerance": 0.01 // Optional, default = 0.01mm
}

center_model

Translate the model so the center of its bounding box is at the world origin (0,0,0).

Copy & paste — that's it
{
 "stl_path": "/path/to/model.stl"
}

lay_flat

Attempt to identify the largest flat surface of the model (that isn't already facing directly up or down) and rotate the model so this face is oriented downwards on the XY plane (Z=0). Useful for orienting models for printing.

Copy & paste — that's it
{
 "stl_path": "/path/to/model.stl"
}

modify_stl_section

Apply a specific transformation to a selected section of an STL file. This allows for detailed modifications of specific parts of a model.

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "section": "top",
 "transformation_type": "scale",
 "value_x": 1.5,
 "value_y": 1.5, 
 "value_z": 1.5
}

For custom section bounds:

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "section": "custom",
 "transformation_type": "rotate",
 "value_x": 0,
 "value_y": 0, 
 "value_z": 45,
 "custom_min_x": -10,
 "custom_min_y": 0,
 "custom_min_z": -10,
 "custom_max_x": 10,
 "custom_max_y": 20,
 "custom_max_z": 10
}

generate_stl_visualization

Generate an SVG visualization of an STL file from multiple angles (front, side, top, and isometric views).

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "width": 400,
 "height": 400
}

slice_stl

Slice an STL file to generate G-code.

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "slicer_type": "orcaslicer",
 "slicer_path": "/path/to/orcaslicer",
 "slicer_profile": "/path/to/machine.json;/path/to/process.json",
 "filament_profile": "/path/to/flat-nylon-filament.json"
}

For OrcaSlicer, the server uses --slice 0 --outputdir and returns the renamed plate_1.gcode output. Load filament separately with filament_profile (--load-filaments) or encode it in slicer_profile after a pipe, for example /path/to/process.json|/path/to/filament.json.

confirm_temperatures

Confirm temperature settings in a G-code file.

Copy & paste — that's it
{
 "gcode_path": "/path/to/file.gcode",
 "extruder_temp": 200,
 "bed_temp": 60
}

process_and_print_stl

Process an STL file (extend base), slice it, confirm temperatures, and start printing.

Copy & paste — that's it
{
 "stl_path": "/path/to/file.stl",
 "extension_inches": 2,
 "extruder_temp": 200,
 "bed_temp": 60,
 "host": "192.168.1.100",
 "type": "octoprint",
 "api_key": "YOUR_API_KEY"
}

Note: Automatic orientation for optimal printing (minimizing supports, etc.) is a complex task typically handled by slicer GUIs (like OrcaSlicer or PrusaSlicer) and is not implemented in this server.

Click to expand Printer Control Tools

Printer Control Tools

get_printer_status

Get the current status of the 3D printer.

Copy & paste — that's it
{
 "host": "192.168.1.100",
 "type": "octoprint",
 "api_key": "YOUR_API_KEY"
}

For Bambu printers, this currently only confirms MQTT connection.

list_printer_files

List files available on the printer.

Copy & paste — that's it
{
 "host": "192.168.1.100",
 "type": "octoprint",
 "api_key": "YOUR_API_KEY"
}

For Bambu printers, lists files in the gcodes directory via FTP.

upload_gcode

Upload G-code content or a local G-code file path to the printer.

Copy & paste — that's it
{
 "host": "192.168.1.100",
 "type": "octoprint",
 "api_key": "YOUR_API_KEY",
 "filename": "my_print.gcode",
 "gcode": "G28\nG1 X100 Y100 Z10 F3000\n...",
 "print": true
}

For larger files, pass a local path instead. If filename is omitted, the printer filename defaults to the basename of gcode_path.

Copy & paste — that's it
{
 "host": "192.168.1.100",
 "type": "klipper",
 "api_key": "YOUR_API_KEY",
 "gcode_path": "/path/to/my_print.gcode",
 "print": true
}

For Bambu printers, uploads to the gcodes directory via FTP. Cannot start print automatically.

start_print

Start printing a file that is already on the printer.

Copy & paste — that's it
{
 "host": "192.168.1.100",
 "type": "octoprint",
 "api_key": "YOUR_API_KEY",
 "filename": "my_print.gcode"
}

Not recommended for Bambu printers. Use print_3mf for Bambu .3mf files.

cancel_print

Cancel the current print job.

Copy & paste — that's it
{
 "host": "192.168.1.100",
 "type": "octoprint",
 "api_key": "YOUR_API_KEY"
}

For Bambu printers, sends the stop_print command via MQTT.

set_printer_temperature

Set the temperature of a printer component.

Copy & paste — that's it
{
 "host": "192.168.1.100",
 "type": "octoprint",
 "api_key": "YOUR_API_KEY",
 "component": "extruder",
 "temperature": 200
}

For Bambu printers, this dispatches firmware G-code temperature commands (M104 for nozzle, M140 for bed) over MQTT.

Click to expand Bambu-Specific Tools

Bambu-Specific Tools

check_fulu_orca_setup

Inspects the FULU OrcaSlicer-bambulab executable, platform runtime payload, setup commands, and optional BambuNetwork bridge probe.

Copy & paste — that's it
{
 "platform": "darwin",
 "slicer_path": "/Applications/OrcaSlicer.app/Contents/MacOS/OrcaSlicer",
 "plugin_dir": "/Applications/OrcaSlicer.app/Contents/MacOS",
 "run_bridge_probe": true,
 "bridge_command": "\"/Applications/OrcaSlicer.app/Contents/MacOS/pjarczak-bambu-linux-host-wrapper\" \"$HOME/Library/Application Support/OrcaSlicer/macos-bridge/runtime/pjarczak_bambu_linux_host\""
}

fulu_bambu_network_rpc

Calls one FULU BambuNetwork bridge JSON RPC method. Read-only methods such as bridge.handshake, bridge.runtime_info, and net.get_user_print_info are allowed by default. Methods that can mutate account, printer, cloud, or print state require allow_mutating_method=true; FULU print methods also require bambu_model.

Copy & paste — that's it
{
 "method": "bridge.handshake",
 "bridge_command": "\"/Applications/OrcaSlicer.app/Contents/MacOS/pjarczak-bambu-linux-host-wrapper\" \"$HOME/Library/Application Support/OrcaSlicer/macos-bridge/runtime/pjarczak_bambu_linux_host\""
}

print_3mf

Uploads a sliced .3mf file to a Bambu printer via FTP and initiates the print job via an MQTT command. If the 3MF has no embedded plate G-code and a project slicer is configured, the server can auto-slice it first with FULU OrcaSlicer-bambulab or Bambu Studio. Allows overriding some print parameters like AMS mapping.

bambu_model is required -- it ensures the slicer generates G-code for the correct printer. Using the wrong model can cause the bed to crash into the nozzle and damage the printer. If not provided in the tool call and BAMBU_MODEL is not set in the environment, the server will ask interactively via MCP elicitation (if supported by your client) or return a clear error.

Copy & paste — that's it
{
 "three_mf_path": "/path/to/your_model.3mf",
 "bambu_model": "p1s",
 "bed_type": "textured_plate",
 "host": "your_bambu_ip",
 "bambu_serial": "YOUR_SERIAL",
 "bambu_token": "YOUR_TOKEN",
 "slicer_type": "orcaslicer-bambulab",
 "slicer_path": "/path/to/FULU/OrcaSlicer",
 "use_ams": true,
 "ams_mapping": [0, 1, 2, 3],
 "bed_leveling": true,
 "flow_calibration": false,
 "vibration_calibration": false,
 "timelapse": false
}

Note: Overriding slicer settings like layer height or temperature via this tool is not supported by the printer's MQTT command. Apply those changes before generating the .3mf file.

Available Resources

Click to expand Printer Resources

Printer Resources

  • printer://{host}/status - Current status of the 3D printer (limited for Bambu currently)

  • printer://{host}/files - List of files available on the 3D printer (FTP for Bambu)

  • printer://{host}/file/{filename} - Content of a specific G-code file (checks existence only for Bambu)

Click to expand Bambu Preset Resources

Bambu Preset Resources

If the BAMBU_STUDIO_CONFIG_PATH environment variable is set to your Bambu Studio user settings directory, you can read your saved presets.

  • preset://bambu/machine/{preset_name} - Reads a machine preset file (e.g., Bambu Lab P1S 0.4 nozzle.json)

  • preset://bambu/filament/{preset_name} - Reads a filament preset file (e.g., Generic PLA.json)

  • preset://bambu/process/{preset_name} - Reads a process preset file (e.g., 0.20mm Standard @BBL P1S.json)

Example Usage: "Read the content of my Bambu process preset named '0.16mm Optimal @BBL P1S'" (Claude would call ReadResource with preset://bambu/process/0.16mm%20Optimal%20%40BBL%20P1S)

Example Commands for Claude

Here are some example commands you can give to Claude after connecting the MCP server:

Printer Control

  • "What's the current status of my 3D printer?"

  • "Show me the list of files on my printer."

  • "Upload this G-code to my printer: [G-code content]"

  • "Start printing the file named 'benchy.gcode'."

  • "Cancel the current print job."

  • "Set the extruder temperature to 200°C."

  • "Set the bed temperature to 60°C."

STL Manipulation and Printing

  • "Take this STL file and extend the base by 2 inches, then send to slicer and queue up in my printer."

  • "Extend the base of model.stl by 1.5 inches."

  • "Scale this STL file by 150% uniformly."

  • "Scale model.stl to be twice as wide but keep the same height."

  • "Rotate this model 90 degrees around the Z axis."

  • "Move this STL model up by 5mm to create a gap underneath."

  • "Can you modify just the top part of this model to make it 20% larger?"

  • "Analyze this STL file and tell me its dimensions and details."

  • "Generate a visualization of this STL file so I can see what it looks like."

  • "Create SVG visualizations of my model from different angles."

  • "Make the base of this model wider without changing its height."

  • "Slice the modified STL file using PrusaSlicer."

  • "Confirm that the temperatures in the G-code are 200°C for the extruder and 60°C for the bed."

  • "Process this STL file, make the base 2 inches longer, slice it, and start printing, but confirm the temperatures first."

  • "Print ~/Downloads/my_model.3mf on the Bambu printer."

  • "Upload ~/Desktop/calibration_cube.3mf to the Bambu printer using AMS slots 0 and 2, and turn off bed leveling."

  • "Cancel the print job on my Bambu P1S."

  • "What are the settings in my Bambu filament preset 'Generic PETG'?"

  • "Show me my Bambu process presets."

Limitations and Considerations

Memory Usage

  • Large STL Files: Processing large or complex STL files can consume significant memory. The entire STL geometry is loaded into memory during operations.

  • Multiple Operations: Running multiple STL operations in sequence (especially on large files) may cause memory to accumulate if garbage collection doesn't keep up.

  • MCP Environment: Since this runs as an MCP server, be aware that Claude's MCP environment has memory constraints. Complex operations on very large STL files may cause out-of-memory issues.

STL Manipulation Limitations

  • Section Modification: The section-specific modification feature works best on simpler geometries. Complex or non-manifold meshes may produce unexpected results.

  • Base Extension: The base extension algorithm works by adding a new geometry underneath the model. For models with complex undersides, results may not be perfect.

  • Error Handling: While we've added robust error handling, some edge cases in complex STL files might still cause issues.

Visualization Limitations

  • SVG Representation: The SVG visualization is a simplified schematic representation, not a true 3D render.

  • Complex Models: For very complex models, the visualization may not accurately represent all details.

Performance Considerations

  • Slicing Operations: External slicer processes can be CPU-intensive and may take considerable time for complex models.

  • Progress Reporting: For large files, progress updates may appear to stall at certain processing stages.

Testing Recommendations

  • Start with smaller STL files (< 10MB) to test functionality

  • Monitor memory usage when processing large files

  • Test modifications on simple geometries before attempting complex ones

  • Consider running on a system with at least 4GB of available RAM for larger operations

Appendix: MCP Safety Notes

See Recommended: use with codemode-mcp for reducing token overhead with large tool surfaces.

Prompt Injection: Risks and Mitigations

Prompt injection is an open problem for tool-using agents. Practical mitigations:

  • Least-privilege credentials and short-lived tokens.

  • Strict schema validation and explicit allowlists for actions/hosts.

  • Human confirmation gates for destructive operations.

  • Execution sandboxing with resource/time limits.

  • Treat tool output as untrusted input by default.

Badges

Badge Description The current version of the package on npm This project is licensed under GPL-2.0 This project is written in TypeScript 4.9+ This project is actively maintained We welcome contributions via Pull Requests Requires Node.js 18.0.0 or higher Number of downloads per month from npm Number of GitHub stars this project has received

License

GPL-2.0