Skip to main content
Glama
Sign In
MichaelGagnon13

cura-mcp

by MichaelGagnon13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cura-mcp

No user-submitted related servers found.

    Related Servers

    • anycubic-slicer-mcp

      EmreTekir
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      9
      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
      1
      MIT

    • orca-mcp

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

    • Bambu Studio MCP

      welingtonmatos
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      11
      MIT

    • nakomis-dragonfruit-mcp

      nakomis
      A
      license
      A
      quality
      B
      maintenance
      Enables an AI assistant to inspect, hollow, check, and slice resin prints headlessly using the DragonFruit engine. It provides tools for mesh information, island detection, hollowing and drilling, printer listing, slicing to printer-specific formats, and previewing/inspecting sliced output.
      3
      AGPL 3.0
    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