Skip to main content
Glama
ShreddyKrueger75

OrcaSlicer MCP

by ShreddyKrueger75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to OrcaSlicer MCP

No user-submitted related servers found.

    Related Servers

    • bambu-mcp

      akashnaren
      A
      license
      A
      quality
      B
      maintenance
      Enables LAN-based monitoring and control of Bambu Lab P2S/P1S printers, including confirm-gated print, pause, resume, stop, file upload, and slicing workflows.
      10
      13 npm
      MIT

    • snapmaker-u1-mcp

      JSCodesTech
      A
      license
      C
      quality
      B
      maintenance
      Enables 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.
      33
      MIT

    • Bambu Printer MCP

      ceweldy
      A
      license
      B
      quality
      C
      maintenance
      Manages, monitors, slices for, and controls multiple Bambu Lab 3D printers with a privacy-focused multi-printer registry and fleet status.
      46
      GPL 2.0

    • orca-slicer-mcp

      dmikushin
      F
      license
      A
      quality
      D
      maintenance
      An 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.
      12
      2
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources