Skip to main content
Glama
MichaelGagnon13

cura-mcp

by MichaelGagnon13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cura-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • orca-mcp

      jeff-roche
      A
      license
      Not graded
      quality
      B
      maintenance
      Wraps the OrcaSlicer CLI to enable AI agents to slice 3D models, run parameter sweeps, and analyze G-code.
      24 PyPI
      1
      MIT

    • orcaslicer-mcp

      Diterex
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to work with OrcaSlicer code and perform slicing operations, such as reading files, checking Git status, and slicing 3D models to get print time and filament usage.
      MIT

    • 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
      -

    • OrcaSlicer MCP

      ShreddyKrueger75
      A
      license
      A
      quality
      B
      maintenance
      Enables headless slicing with OrcaSlicer, preset management, G-code analysis, and printer control over LAN for Klipper, OctoPrint, Prusa, Duet, Elegoo, and Bambu printers.
      15
      3
      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

    B3/5.0

    Scored across 12 tools

    Disambiguation3/5

    There is clear overlap between 'cura_slice' and 'slice' both performing slicing operations, and 'cura_arrange' vs 'make_project' both involve part positioning. Other tools have distinct purposes, but these overlaps create ambiguity for an agent.

    Naming Consistency2/5

    Naming is inconsistent: most tools use 'cura_' prefix (cura_arrange, cura_get, etc.), but four tools (get_profile, list_printers, make_project, slice) lack the prefix. All use snake_case, but the prefix inconsistency is confusing.

    Tool Count4/5

    12 tools is appropriate for a Cura MCP server, covering loading, slicing, settings, and status. The count feels slightly padded due to duplicate slicing tools, but is still within a reasonable range.

    Completeness2/5

    Obvious gaps: no tool to set active printer, remove models, export gcode, or adjust individual model settings. The duplicate slicing tools waste a slot while missing core lifecycle operations, leading to potential agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources