Ultimaker-S5-Interfacing
Related Servers
Alternatives to Ultimaker-S5-Interfacing
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables secure local control of Anycubic Slicer Next and compatible printers, supporting slicing, 3MF/CAD operations, printer control, spool registry, and camera access through MCP tools.1MIT
- AlicenseAqualityCmaintenanceEnables 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.15MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to create and edit parametric FreeCAD models, run Python inside FreeCAD, capture viewport screenshots, inspect documents, execute headless scripts, and run FEM analyses.171MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to slice STL/3MF models through an official, unmodified slicer CLI, list machine/process/filament profiles, apply setting overrides, and inspect G-code statistics.10MIT
- AlicenseBqualityBmaintenanceEnables 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.305,162 npm266GPL 2.0
- AlicenseCqualityBmaintenanceEnables 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.63AGPL 3.0
TDQS
Scored across 18 tools
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.
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.
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.
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.