Skip to main content
Glama
Ultimaker-S5-Interfacing
by mjklopfer

Cura MCP

A local MCP platform for the UltiMaker S5 and Cura, with a loopback Cura plugin, a dependency-free Node stdio MCP server, guarded printer operations, and S5 R1 hardware/protocol research. Independent community project; not affiliated with or supported by UltiMaker.

Reference configuration

Component

Version

Printer

UltiMaker S5 R1

Printer firmware

9.0.3.0

UltiMaker Cura

5.14.0

These are the versions used for the documented integration. Other versions require validation; see tested versions.

Related MCP server: anycubic-slicer-next-control

What it provides

  • Inspect Cura's machine, extruders, settings, scene and slicer state.

  • Load models/projects, change settings, request slicing and export G-code.

  • Place and transform models, set per-model overrides, select profiles, inspect layers, capture previews, and compare slicing variants using the sample STL.

  • Discover native extension menus and queue local Cura package operations.

  • Save a native full-workspace 3MF project: Save, Save As with a new filename, Save As in another folder, and asynchronous completion/status.

  • Inspect a catalog of 130 local API paths / 161 HTTP operations, including queue/status, temperatures, materials, diagnostics and system configuration.

  • Read bounded printer endpoints and perform explicitly confirmed writes through the catalog. Upload and start are separate actions; uploading may still trigger the printer's own queue policy when idle.

  • Review original S5 R1 PCB/serial/GPIO notes and a disabled-by-default two-STM32 UMB accessory-controller draft with separate Air Manager and Material Station roles.

  • Follow optional developer SSH procedures for Linux/service/device inspection, D-Bus diagnostics and actual printer-touchscreen capture.

Configure your printer address during deployment. See the deployment guide for setup and connection requirements.

MCP client --stdio--> Node MCP server --loopback token--> Cura plugin --> Cura
                              |
                              +--configured LAN HTTP API--> S5

Start here

  1. Read the Windows/Mac configuration comparison, macOS guide, Windows guide and deployment and install the plugin while Cura is closed.

  2. Set CURA_PRINTER_BASE_URL, the staging folder and connection-file path.

  3. Start node src/server.mjs through your MCP client's stdio configuration.

  4. Begin with cura_status and printer_api_catalog. Writes require exact-action authorization and a matching short-lived confirmation token.

See the 26-tool reference, tested versions, known shortcomings and TODOs, and security/privacy. These upstream repositories are particularly relevant to extending the bridge and investigating the printer hardware:

Repository

Why it is useful

Cura / Uranium

Native APIs for object movement/undo, profile selection, slicing and printer-upload workflows; foundations for additional bridge endpoints.

CuraLiveScriptingPlugin

Examples of accessing Cura settings and application internals. Older SDK/QML and background script execution require review before reuse.

um-kernel

A20-era device trees, board identification, boot and recovery handling. A separate newer-board UMB drive-enable fix offers a tracing clue, not an R1 pinout.

UltimakerMarlin

Motion/heater interfaces and print-core EEPROM command handlers; upstream code must be checked against installed firmware.

nfc_test / m2m_certificates

Direct-reader NFC test configuration and NDEF certificate formats; neither establishes the complete Material Station UMB implementation.

oib_testbench / Ultimaker3 hardware

Older interface-board GPIO/loopback and hardware references for tracing related circuitry; not a verified S5 R1 schematic.

ulticontroller_interface_tester / framebuffer-vncserver

Touchscreen diagnostics and remote display/input references; actual S5 UI routing and compatibility still need validation.

See the upstream research map for inspected files, version references and unresolved questions. These are research references; their features are not all implemented or validated by this project. Hardware notes start at S5 R1 interfaces; the UMB controller is a separate offline draft. See miscellaneous notes for print-core identity versus Cura settings, source-observed EEPROM commands and the older UM2 board reference. For optional printer-side screen capture and experimental UI input, see developer-mode touchscreen access. The SSH access and capabilities guide explains the broader Linux troubleshooting/maintenance access and its limits; SSH is not an additional implemented MCP tool.

Requirements and checks

  • Cura 5.14.0 is the live test target for this release. For a 5.13 installation, set CURA_MCP_CURA_VERSION=5.13 for the installer and MCP runtime. An explicit CURA_MCP_BRIDGE_CONNECTION_PATH overrides the runtime default.

  • See version differences for the 5.13 and 5.14 deployment requirements. The scene operations, configuration and profiles, and navigation and extensions notes cover the desktop tools and their parameters.

  • Node.js 20+ and Python 3.10+; Cura supplies its own Qt/Python plugin runtime.

  • macOS Keychain or Windows Credential Manager for printer Digest pairing.

  • A C++11 compiler is needed only for the optional offline controller tests.

From the repository root:

node --test
python -m unittest discover -s tests -p 'test_*.py'
python scripts/privacy_check.py

From hardware/umb-controller, run python tools/run_tests.py for native/stub controller checks. These tests do not connect to a real printer. Never treat offline tests, an accepted request or a sliced file as proof of a successful print.

Release and attribution

Release 0.1.12 adds native camera discovery, multi-camera stills and print progress alongside preinstalled cloud printer selection and native cloud printing to the Cura 5.14.0 platform and includes an original STL sample for testing slice comparisons. The repository also includes the two-STM32 controller draft and hardware/NFC research. See changelog, sanitization policy, source references, notices and MIT license. Vendor firmware, recovery images, service source dumps, raw device captures, third-party model files and proprietary schematics are not redistributed.

Available Tools

18 tools
confirm_cura_operationA
Destructive

Prepare a five-minute one-use confirmation for exact settings, slicing, G-code export or project Save/Save As. Project confirmation shows the resolved destination and binds existing-file SHA256. Show the changes before executing.

Inputs: action (required), mode, folder, values, +5 more.

confirm_printer_api_writeA
Destructive

Prepare a one-use five-minute confirmation bound to the exact documented write request and current printer state. Show the request and effect to the human and obtain specific approval before printer_api_write. Does not perform the write.

Inputs: api (required), method (required), endpoint (required), body, +4 more.

create_cura_confirmationConfirm Cura workspace writeA

Create a one-use confirmation token for loading one staged file into Cura. This does not modify Cura.

Inputs: action (required), file_path (required), project_mode.

create_print_confirmationConfirm printer write actionA

Create one short-lived token for a specific staged toolpath upload or queued-job print start after reading printer status. Performs no printer write. Show the human the target and warning before using the write tool.

Inputs: action (required), job_uuid, file_path.

cura_inspectB
Read-only

Read the live Cura machine/profile, extruders/materials, scene objects, backend state and sliced build plates, explicitly on its main thread.

Inputs: no named parameters.

cura_operationA
Destructive

Apply approved Cura settings, slice, export G-code, or save a full 3MF project. Project saves return an operation_id; poll cura_project_save_status for completion. Never prints or uploads automatically.

Inputs: action (required), confirmation_token (required), mode, folder, +6 more.

cura_path_infoA
Read-only

Inspect one absolute path from Cura itself: existence, type, readability, resolved path and OS error. Does not return file contents.

Inputs: file_path (required).

cura_project_save_statusA
Read-only

Read completion, validated archive size/hash or failure for a project save. A running response is not a completed save.

Inputs: operation_id (required).

cura_settingsA
Read-only

Read effective global or extruder settings. Omit keys to list available setting keys; provide at most 200 keys for values.

Inputs: keys, extruder.

cura_statusCura statusA
Read-only

Check whether the local Cura bridge is ready. Printer/profile/extruder/scene fields are placeholders, not live measurements; startup deliberately avoids inspecting Cura configuration. Does not modify Cura or contact a printer.

Inputs: no named parameters.

load_cura_fileLoad staged file into CuraB
Destructive

Loads one confirmed staged model, project, G-code, or UFP file into the active Cura workspace. It does not slice or send a print.

Inputs: file_path (required), confirmation_token (required), project_mode.

preflight_print_actionPreflight printer write actionB

Check whether an upload or print-start operation is currently safe. It performs no write.

Inputs: action (required).

printer_api_catalogB
Read-only

Inspect all documented local S5 printer/cluster R/W endpoints and schemas. Specify api + endpoint to include operation details and definitions.

Inputs: api, endpoint.

printer_api_readB
Read-only

GET a documented bounded local printer endpoint. Does not support unbounded camera streams. May return network/system details; request only what is needed.

Inputs: api (required), endpoint (required), body, form, +3 more.

printer_api_writeA
Destructive

Execute an explicitly approved documented S5 write with its matching confirmation token. Includes motion, temperature, pause/abort/resume, jobs/materials/configuration/firmware/network operations. Do not invoke without the human approving the exact action. Auth pairing stores credentials in the OS credential store and needs approval on the printer display.

Inputs: api (required), method (required), endpoint (required), confirmation_token (required), +5 more.

printer_statusUltiMaker printer statusA
Read-only

Read the Cura Connect printer inventory and its active and queued jobs. This tool performs no printer write.

Inputs: no named parameters.

start_printStart a queued printer jobB
Destructive

Commands one confirmed queued local printer job to start printing.

Inputs: job_uuid (required), confirmation_token (required).

upload_gcodeUpload staged toolpath to printer queueA
Destructive

Uploads one confirmed .gcode, .gcode.gz, or .ufp file from the staging folder to the selected local printer. It may start automatically if the printer queue policy permits it.

Inputs: file_path (required), confirmation_token (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 18 tools

    Disambiguation4/5

    Each tool targets a fairly distinct resource+action, and descriptions carefully delimit read vs. write. However, there are four confirmation/token tools (create_cura_confirmation, create_print_confirmation, confirm_printer_api_write, confirm_cura_operation) that serve subtly different flows and could be mis-selected. Read tools like cura_status, cura_inspect, and cura_settings are close but adequately differentiated.

    Naming Consistency3/5

    A domain-prefix convention (cura_*, printer_*) is visible and readable, but verb styles are mixed: verb_noun (start_print, load_cura_file, upload_gcode) alongside noun_status patterns (printer_status, cura_status, cura_project_save_status). It is understandable but not a single predictable pattern.

    Tool Count4/5

    18 tools is slightly heavy but justified by the domain: a Cura bridge plus a printer API plus a two-step human-confirmation safety model that requires paired confirm/execute tools. Each tool roughly earns its place, though the confirmation duplication inflates the count a bit.

    Completeness4/5

    The surface covers the full lifecycle: staging/loading files, upload, print start, status, Cura settings/slicing/export/save, and arbitrary documented printer reads/writes (including pause/abort/resume). Minor gaps like job deletion or richer scheduling are largely absorbable via printer_api_write.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables interaction with 3D printer management systems through an MCP server, supporting STL file manipulation, slicing, and control of printers like OctoPrint, Klipper, Duet, and more.
      30
      5,162 npm
      266
      GPL 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to inspect FreeCAD documents and export named solids to STL, find and derive OrcaSlicer presets, preview and run slices with recorded manifests, and then read G-code metadata, query a Moonraker printer, upload G-code, and start an uploaded print as a separate confirmed step.
      15
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables MCP clients to drive a separately installed OrcaSlicer instance through a local stdio server, covering slicing jobs, profile and 3MF/settings editing, raw CLI options, artifact inspection and an optional desktop adapter for GUI actions. It also provides job queuing, status tracking and runtime detection of the installed binary's capabilities.
      63
      AGPL 3.0