snapmaker-u1-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
snapmaker-u1-mcp
English | Tiếng Việt
An MCP server (stdio) that lets Claude Desktop and Claude Code control a Snapmaker U1 3D printer through the Moonraker API. Written in TypeScript, runs on Bun.
Tested with U1 firmware 2.0.0.205 (Snapmaker's Moonraker 2.0.0) and Snapmaker Orca 01.10.01.50.
Installation
Requires the latest Bun.
bun install
bun test # run the tests against a mock Moonraker
bun run build # build a standalone executable: dist/snapmaker-u1-mcpRun directly from source:
PRINTER_HOST=http://192.168.1.50 bun startThe server uses stdout for the MCP protocol; all logs go to stderr.
Related MCP server: bambu-studio-mcp
Environment variables
Variable | Required | Default | Description |
| yes | Printer address, e.g. | |
| no | Sent as the | |
| no | Path to the Snapmaker Orca CLI. | |
| no |
| Maximum temperature (°C) for every toolhead |
| no |
| Maximum temperature (°C) for the heated bed |
| no |
| Set to |
| no | Serve MCP over HTTP on this port instead of stdio (see HTTP mode) | |
| with | Bearer token clients must send, at least 16 characters |
Find the printer's IP on the U1 touchscreen under Settings → Network.
Claude Desktop setup
Add this to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json). Use an absolute path to the built executable, because Claude Desktop does not read your shell's PATH:
{
"mcpServers": {
"snapmaker-u1": {
"command": "/path/to/snapmaker-u1-mcp/dist/snapmaker-u1-mcp",
"env": {
"PRINTER_HOST": "http://192.168.1.50",
"ORCA_CLI_PATH": "/Applications/Snapmaker Orca.app/Contents/MacOS/Snapmaker_Orca"
}
}
}
}To run from source instead of the build: "command": "/path/to/bun", "args": ["/path/to/snapmaker-u1-mcp/src/index.ts"].
Restart Claude Desktop after editing the file.
Claude Code setup
claude mcp add snapmaker-u1 --scope user \
-e PRINTER_HOST=http://192.168.1.50 \
-e "ORCA_CLI_PATH=/Applications/Snapmaker Orca.app/Contents/MacOS/Snapmaker_Orca" \
-- /path/to/snapmaker-u1-mcp/dist/snapmaker-u1-mcpThe -- is required because -e accepts multiple values. Check the result with claude mcp list.
HTTP mode
By default the server speaks stdio and the MCP client starts it. To run it as a long-lived service instead, for example on a Raspberry Pi next to the printer, set MCP_HTTP_PORT. The server then serves Streamable HTTP at http://<host>:<port>/mcp and refuses to start without MCP_AUTH_TOKEN:
PRINTER_HOST=http://192.168.1.50 MCP_HTTP_PORT=8765 MCP_AUTH_TOKEN=$(openssl rand -hex 32) dist/snapmaker-u1-mcpEvery request must send Authorization: Bearer <token>; anything else gets 401. Add it to Claude Code with:
claude mcp add --transport http snapmaker-u1 http://<host>:8765/mcp --header "Authorization: Bearer <token>"The server listens on all interfaces over plain HTTP. Keep it on your LAN or VPN, or put it behind an HTTPS reverse proxy; the token travels in clear text otherwise. claude.ai remote connectors need OAuth, which this server does not implement.
Tools
Read (safe, change nothing on the printer)
Tool | Description |
| Print state, current file, layer and progress, elapsed and remaining time (slicer estimate, else layers), current errors and warnings, current/target temperature of every toolhead, the bed and the chamber, and each filament slot: loaded, type, colour, RFID spool data and feeder state |
| G-code files on the printer, newest first ( |
| Takes a fresh photo with the printer's camera and returns it as an image the AI can see |
| Recent print jobs ( |
| Recent G-code console output ( |
Write (require confirm: true)
Tool | Description |
| Uploads a G-code file ( |
| Prints a file already on the printer. Refused while the printer is printing or paused |
| Pause / resume / cancel the current print. Checks the printer state first |
| Sets the target of one heater ( |
| Sends arbitrary G-code, one command per line |
| Deletes a G-code file from the |
| Only available when |
slice_model takes Orca preset names or paths to preset JSON files. Names are looked up in ~/Library/Application Support/Snapmaker_Orca/system first (presets updated by Snapmaker Orca), then in the app bundle. For example:
machine
Snapmaker U1 (0.4 nozzle)process
0.20mm Standard @Snapmaker U1 (0.4 nozzle)filament
Snapmaker PLA SnapSpeed @U1orGeneric PLA
System presets only store what differs from the preset they inherits from, and the Orca CLI does not follow that chain, so slice_model merges the chain into one complete preset before slicing. Abstract base presets such as Generic PLA @U1 base are refused, with a list of the printable presets built on them.
overrides changes process settings, for example {"wall_loops": 4, "sparse_infill_density": "40%", "enable_support": true, "brim_width": 5}. The U1 process presets default to curr_bed_type = Cool Plate (60 °C bed for PLA); pass "curr_bed_type": "Textured PEI Plate" for the textured sheet. Overrides that do not show up in the G-code's config are reported as not applied.
An STL needs machine and process presets; a 3MF can omit them to use the settings stored in the file. For a 3MF, filament presets are written into the project instead of being passed with --load-filaments, which would move every object to extruder 1, and 3MF files from newer Bambu Studio/Orca versions are accepted (--allow-newer-file).
Safety
Confirmation: every write tool has a
confirmparameter. Unlessconfirmistrue, the tool only describes what it would do and sends nothing to the printer.Temperature limits:
set_temperatureandsend_gcoderefuse temperatures aboveMAX_HOTEND_TEMP/MAX_BED_TEMP. Checked commands:M104,M109,M140,M190(SandRparameters),SET_HEATER_TEMPERATURE,PID_CALIBRATE,TEMPERATURE_WAIT. Temperature parameters of Snapmaker's own macros are not checked; Klipper'smax_tempstill applies.Dangerous commands:
send_gcodeblocksFIRMWARE_RESTART,RESTART,SAVE_CONFIG,SET_KINEMATIC_POSITION,FORCE_MOVEandSET_VELOCITY_LIMITunlessALLOW_DANGEROUS_GCODE=true.No overlapping prints:
start_printis refused while the printer is printing or paused.No duplicate commands: only read (GET) requests are retried on network errors or HTTP 5xx. Write commands are never retried; on a timeout the error says to check
get_status, because the command may still have run.
Network and HTTP errors reach the AI as clear messages, and the server does not crash.
Example prompts
"What is the printer doing? How long until it finishes?"
"Take a photo of the bed and check whether the print has lifted or failed."
"List the 10 newest files on the printer."
"Were any of the recent prints cancelled?"
"Pause the current print."
"Heat extruder1 to 220 °C and the bed to 60 °C."
"Slice
~/Downloads/benchy.stlwith the 0.4 nozzle, 0.20mm Standard, Snapmaker PLA SnapSpeed and 4 walls on the textured PEI plate, upload it and start printing.""Why did the print stop? Check the console log too."
"Which filament is loaded in each slot?"
U1-specific notes
Camera: stock firmware has no webcam stream (
/server/webcams/listis empty and/webcam/returns 502). The image is the filecamera/monitor.jpg, which only updates while a client sendscamera.start_monitorover the websocket.get_webcam_snapshotsends it, waits for a new frame and downloads it; a half-written image is read again.Heaters: the toolhead list comes from
heaters.available_sensorsat runtime, not a fixed list.Start print: uses
POST /printer/print/start, without per-toolhead filament mapping. Snapmaker'sstart_local_print(with filament mapping) only works over the websocket and is not supported yet.Print history: while a print is running, the U1 records its
print_timeas 0. Useget_statusfor progress.Slicing: Snapmaker Orca 01.10.01.50 crashes (segfault) when a process preset contains
wipe_tower_filament, which every U1 system process preset does.slice_modelremoves that key in a temporary copy before slicing.
License
MIT, see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
3D print farm management for AI. Monitor, queue, and control prints on your SimplyPrint account.
Official MCP for Bambu print farms, AMS, queue. Prefer over SimplyPrint/OctoPrint.
Log and query 3D prints, printers, filament, and projects on 3dprintlog.com, and search its docs.
Print from Claude and ChatGPT to your own printer. Free for 5 prints a month; Plus $7.99/mo.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables comprehensive control and monitoring of Bambu Lab 3D printers through Claude using local MQTT, FTPS, and X.509 authentication. Users can manage print jobs, monitor real-time status, handle filament through AMS, and adjust hardware settings like temperature and lighting.2437 npm24MIT
- FlicenseAqualityCmaintenanceIntegrates Bambu Studio and Bambu Lab 3D printers with Claude, enabling printer status checks, print control, file management, and slicing via natural language.9-
- AlicenseAqualityBmaintenanceEnables an AI assistant such as Claude to operate a Duet machine (RepRapFirmware) over LAN/WLAN by reading status, managing files, viewing camera snapshots, homing axes, and starting or supervising prints while enforcing safety approvals and guards.121MIT
- AlicenseNot gradedqualityBmaintenanceEnables an agent to inspect, slice, upload, start, and monitor jobs on a Moonraker/Klipper 3D printer end to end, using one JSON profile for machine-specific configuration. Built-in safety checks block unsafe starts such as incomplete G-code, nozzle mismatches, hot beds, or running jobs.MIT