Skip to main content
Glama
dmikushin

orca-slicer-mcp

by dmikushin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to orca-slicer-mcp

No user-submitted related servers found.

    Related Servers

    • orcaslicer-mcp

      MaxEllis
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets Claude drive a real, running OrcaSlicer: load models, arrange the plate, tune settings, slice, and read results back.
      44
      193 PyPI
      57
      AGPL 3.0

    • Klipper MCP Server

      Charleslotto
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI assistants to control and monitor Klipper 3D printers via the Moonraker API. It supports comprehensive printer management, including G-code execution, toolchanger operations, and real-time status monitoring.
      25
      -

    • MCP 3D Printer Server

      DMontgomery40
      A
      license
      B
      quality
      A
      maintenance
      Enables 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.
      30
      393 npm
      243
      GPL 2.0

    • spz-mcp

      redDwarf03
      A
      license
      A
      quality
      B
      maintenance
      MCP server that lets an LLM agent drive StableProjectorz, a 3D modeling app, by inspecting the loaded model, app state, viewport screenshots, and triggering UI actions via a loopback socket bridge.
      1
      1
      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
    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 12 tools

    Disambiguation5/5

    Each tool has a distinct purpose: UI actions (click, press_key, type_text), file operations (export_gcode, import_model, process_model), session management (start/stop_session, session_status), printer control (print_gcode), view manipulation (zoom), and capture (screenshot). No overlapping functionality.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., import_model, start_session). However, 'screenshot' is a noun, 'zoom' is a single verb, and 'session_status' uses noun_noun, introducing a few inconsistencies.

    Tool Count5/5

    12 tools cover the core workflow (session lifecycle, model import, slicing, printing, UI interaction) without being excessive. Each tool justifies its existence for automating OrcaSlicer.

    Completeness4/5

    The set covers major workflows but lacks direct tools for model editing (e.g., scale, rotate) and printer status. However, UI tools like click and press_key can compensate, and the core slice-and-print path is complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources