Anycubic Slicer MCP
Related Servers
Alternatives to Anycubic Slicer MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI agents to perform reproducible Snapmaker U1 headless slicing with Snapmaker Orca, including model/profile discovery, STL/3MF-to-G-code slicing, G-code analysis, controlled overrides, and slice or orientation comparisons without GUI automation or printer control.331MIT
- AlicenseAqualityCmaintenanceEnables AI agents to control Anycubic Slicer Next without its GUI by listing presets, slicing models, reading print-time and filament estimates, and rendering toolpath previews.91MIT
- AlicenseBqualityDmaintenanceEnables AI agents to slice 3D models (STL files) headlessly using UltiMaker Cura's CuraEngine, returning ready-to-print G-code and estimated print time.12AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceLets MCP clients such as Claude drive the PrusaSlicer 2.9.x command-line interface headlessly: discovering installed printers and profiles, inspecting and previewing models, suggesting print orientation, slicing with real presets, and reading back print time and filament use. Runs slicing as a separate process so the GUI can stay open, and supports transforms, hole capping, and 3MF projects that keep their saved settings.MIT
- 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
- AlicenseAqualityCmaintenanceEnables LLM clients to slice, paint, and verify 3D prints through the installed slicer's command line for any installed Bambu printer, nozzle, and filament, with settings per object type. It never sends jobs to a printer.11MIT
TDQS
Scored across 25 tools
Descriptions explicitly cross-reference and separate overlapping tools (model_info vs check_bed_fit, compare_slices vs slice_model, preview_gcode vs animate_layers vs print_card, find_best_orientation vs analyze_strength), so an agent can pick correctly. Cost reporting appears in several tools (estimate_cost, gcode_summary, print_card, compare_slices), but each is scoped to a distinct workflow.
All names are snake_case and mostly readable, but the ordering is mixed: verb_noun (slice_model, list_presets, check_bed_fit) alongside noun_noun (model_info, gcode_summary, print_card, slicer_status). Still predictable enough to infer purpose, just not a single consistent pattern.
25 tools is at the heavy end for a single server. The breadth (slicing, preset management, spool inventory, diagnosis, calibration, multicolor, project planning) justifies most tools, but the surface is large and borderline for a slicer domain.
Covers the full lifecycle: model analysis, orientation/strength guidance, slicing (single, comparison, project), preset read/write, spool inventory CRUD, G-code inspection/visualization, failure diagnosis, calibration, and multi-color optimization. No obvious dead ends remain for a local slicing workflow.