Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-server-qidi is my QIDI printer still printing? show me the chamber webcam"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for a QIDI X-Plus5 (Klipper + Moonraker) 3D printer: status, chamber webcam, QIDI Box, G-code files and job history, plus gated control (light, heater targets, pause/resume/cancel, emergency stop, start print).
Moonraker on the Plus5 trusts every LAN client and has no credentials. The printer's privacy therefore rests on the network path (in our deployment a WireGuard tunnel scoped to the printer's single address) and on the Entra-authenticated gateway in front of this server.
Tool | Tier | |
| read | Printer reachable? Which tiers are on, temperature limits. |
| read | State, file, progress, layer, time left, nozzle/bed/chamber temps, loaded Box slot. |
| read | Chamber webcam picture ( |
| read | QIDI Box slots: material, colour, inserted, humidity, drying. |
| read | G-code on the printer; slicer estimate, filament, temps. |
| read | Recent jobs with result, duration and filament. |
| read | Last console lines — read this when a start failed. |
| control | Chamber light on/off. |
| control | Nozzle/bed/chamber target, capped by |
| control | |
| control | Must name the running file, so a stale conversation cannot cancel the wrong job. |
| control | M112 and recovery. Restart is refused while printing. |
| Start a file already on the printer. See the plate check below. |
There is deliberately no raw G-code tool: every command sent to the printer is built from enumerated input.
Nobody is standing next to the printer when a print is started from Claude.
qidi_start_print refuses unless:
the printer is idle (standby, complete, cancelled or error),
a qidi_snapshot was taken in the last QIDI_PLATE_CHECK_MAX_AGE_MIN minutes
(default 15) and after the previous job ended — so whoever starts a print
has been shown the plate after the last part came off it,
the caller passes plateIsEmpty: true, and
the file exists on the printer.
A snapshot is good for one start.
Related MCP server: PrusaLink MCP
Env var | Default | |
|
| Moonraker base URL. |
|
| mjpeg-streamer snapshot. |
| — | Sent as |
|
| Light, temperatures, pause/resume/cancel, e-stop, restart. |
|
|
|
| 300 / 110 / 65 | Remote target caps (°C). |
|
| Snapshot freshness for a start. |
|
| Per-request timeout. |
| — | JSONL audit log (who did what; Moonraker logs everything as |
|
| Trust |
| — | Bearer the gateway must present (HTTP transport). |
npm install
npm run typecheck && npm test && npm run build
QIDI_MOONRAKER_URL=http://<printer>:7125 npm run dev # stdioApache-2.0
Filament in each QIDI Box slot (vendor, material, colour, whether filament is inserted), which slot is loaded, box humidity, temperature and drying state.
Inputs: no named parameters.
Cancel the running or paused print. Cannot be undone: the job is lost. Pass the file name of the running job to confirm which job you mean.
Inputs: filename (required).
The last lines of the printer console (G-code responses and errors). Read this when a print failed to start or stopped unexpectedly.
Inputs: count.
Immediately halt the printer (M112): heaters and motors stop and the job is lost. Only for a real problem (spaghetti over the hotend, crash, smoke). Afterwards the printer needs qidi_firmware_restart.
Inputs: reason (required).
Slicer metadata for one file: estimated print time, filament type/name/weight, temperatures, layer height, object height.
Inputs: filename (required).
Restart Klipper firmware after an emergency stop or an error/shutdown state. Refused while a job is printing or paused.
Inputs: no named parameters.
Recent print jobs, newest first: file, result, start/end time, print duration and filament used.
Inputs: limit.
G-code files on the printer, newest first. Optional case-insensitive name filter.
Inputs: limit, filter.
Pause the running print (the printer parks the nozzle). Resume with qidi_resume_print.
Inputs: no named parameters.
Current state of the QIDI X-Plus5: job state, file, progress, layer, elapsed and estimated remaining time, nozzle/bed/chamber temperatures and targets, loaded QIDI Box slot, light.
Inputs: no named parameters.
Resume a paused print.
Inputs: no named parameters.
Which printer this server talks to, which tool tiers are switched on, and whether the printer answers.
Inputs: no named parameters.
Switch the chamber light on or off.
Inputs: on (required).
Set the target temperature of the nozzle, bed or chamber heater (0 = off). Targets above the server limits are refused. Typical use: switch heaters off, or restore a chamber target that something else reset during a print.
Inputs: heater (required), target (required).
Take a picture with the chamber webcam. Use it to check that the build plate is empty before starting a print, or to look at a running print. Set light=true to switch the chamber light on first (needs the control tier); the picture is dark without it.
Inputs: light.
Start printing a G-code file that is already on the printer. Before calling: take qidi_snapshot (light=true) and LOOK at the picture — the plate must be empty. The server refuses unless a snapshot was taken in the last few minutes and after the previous job ended, and the printer is idle. After starting, check qidi_printer_status again after ~4 minutes (heating + probing) before reporting that the print is running.
Inputs: filename (required), plateIsEmpty (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 16 tools
The tools split cleanly by purpose: server/tier status vs. live printer state, box filament info, file listing/metadata, history, console diagnostics, and distinct control actions. A minor overlap exists because qidi_snapshot can switch the light on, but the description makes qidi_set_light the dedicated light-control tool.
All tools use the same qidi_ prefix and snake_case convention, with predictable verb_noun or noun_status forms such as qidi_set_light, qidi_list_files, and qidi_printer_status. A few noun-only names like qidi_snapshot and qidi_console are still clear and consistent with the overall pattern.
At 16 tools this is slightly above the typical 3-15 well-scoped range, but each tool maps to a distinct printer monitoring or control function and there is little obvious filler. The count is reasonable for a printer control server, though a few tools could be consolidated if simplicity were prioritized.
The surface covers monitoring and job lifecycle well: status, snapshot, files, metadata, history, console, temperature, light, start, pause, resume, cancel, emergency stop, and firmware restart. However, notable gaps remain around file lifecycle management (upload/delete) and hardware operations such as filament load/unload or motion/jog/calibration.
Official MCP for Bambu print farms, AMS, queue. Prefer over SimplyPrint/OctoPrint.
3D print farm management for AI. Monitor, queue, and control prints on your SimplyPrint account.
Log and query 3D prints, printers, filament, and projects on 3dprintlog.com, and search its docs.
Control your existing Philips lights, Sonos speakers, Roborock vacuums and other supported devices through Port OS cloud. Give ChatGPT, Claude and other MCP-compatible assistants access to the devices you connect. Turn off the living room lights, play music on your speakers, adjust the thermostat, run a vacuum in a room, check a camera snapshot or find a connected tracker. Available actions depend on your linked provider accounts and each device’s supported capabilities. Port OS runs in the cloud; no local server is required. You choose the account, device and capability permissions each assistant receives. Device operations require user OAuth; public tool discovery does not grant device access. Port OS is in alpha. Setup: https://portoperatingsystem.com/docs/getting-started/ Support: https://portoperatingsystem.com/contact/
