creator5-slicer-mcp
Related Servers
Alternatives to creator5-slicer-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn intelligent 3D printing assistant that enables users to analyze meshes, generate optimal print profiles, and automate PrusaSlicer operations through an MCP client. It provides a comprehensive suite of tools for geometric analysis, printability checks, filament recommendations, and post-print diagnostics.1710-
- 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
- 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
- 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
- AlicenseNot gradedqualityBmaintenanceExposes MCP tools that slice models with headless OrcaSlicer, stage gcode on Moonraker-based Klipper printers, gate job starts behind explicit operator authorization, and report status, telemetry-derived events, snapshots, and alerts. It also manages spools and lets AI agents query job estimates, blockers, and start-precondition checks.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables plain-English slicing guidance, profile discovery and comparison, 3MF/STL inspection and optimization, headless slicing with cost/time metrics, GUI automation, and live printer/AMS monitoring and control for Bambu Lab 3D printers.MIT
TDQS
Scored across 8 tools
The tools split into setup/inspection (check_setup, list_filaments, printer_status), planning (analyse_model, recommend_settings) and execution (slice_model, open_in_slicer, send_to_printer), so most purposes are distinct. There is some overlap around readiness and presets between check_setup, list_filaments and printer_status, and recommend_settings versus slice_model share many arguments, but the descriptions clarify the intended boundaries.
Most names follow a verb_noun pattern: check_setup, list_filaments, analyse_model, recommend_settings and slice_model. The deviations are printer_status (a noun phrase) and open_in_slicer/send_to_printer (verb_to_noun), but the overall convention is still predictable and readable.
Eight tools is well-scoped for a slicer/printer workflow, with each tool mapping to a clear stage: setup check, filament listing, model analysis, recommendation, slicing, opening, status and sending. There are no obvious filler tools.
The surface covers the main lifecycle from setup verification and model analysis through slicing, opening in the slicer and sending to the printer. Minor gaps remain around print-job control such as pause/cancel/progress, and the experimental status/send tools may force agents back to the slicer UI or printer controls for job management.