OrcaSlicer MCP
Related Servers
Alternatives to OrcaSlicer MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.MIT
- AlicenseBqualityCmaintenanceManages, monitors, slices for, and controls multiple Bambu Lab 3D printers with a privacy-focused multi-printer registry and fleet status.46GPL 2.0
- AlicenseAqualityDmaintenanceEnables AI agents to interact with OrcaSlicer to manage profiles, adjust printing settings, and perform slicing operations. It allows users to search settings, slice STL/3MF files, and analyze G-code metadata through natural language assistants.7AGPL 3.0
- FlicenseAqualityCmaintenanceAn MCP server that drives OrcaSlicer headlessly on a virtual display, enabling an agent to import 3D models, slice them, and export G-code without a physical screen or GUI automation.122-
- FlicenseAqualityCmaintenanceEnables remote cloud control and live LAN camera access for Bambu Lab 3D printers through 31 MCP tools.31-
- AlicenseNot gradedqualityBmaintenanceEnables 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.57 npm236GPL 2.0
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose (e.g., analyzing G-code vs. slicing, controlling prints vs. starting them). No two tools appear to do the same thing, and even closely related tools like printer_status and printer_attributes serve different informational needs.
Most tools follow a verb_noun pattern (e.g., configure_printer, list_profiles, slice_model). A few use noun_noun (e.g., gui_project_state, printer_status, printer_files), creating minor inconsistency. Still, the naming is clear and readable.
15 tools cover the essential operations for a 3D printing server (slicing, analysis, configuration, control, file management, monitoring) without redundancy. The count is well-scoped for the domain.
Core workflows (slice, upload, start, control, analyze, manage presets) are covered. Minor gaps exist, such as the absence of a delete file tool, but the overall surface is sufficient for most remote 3D printing tasks.