Skip to main content
Glama
JSCodesTech

snapmaker-u1-mcp

by JSCodesTech

Related Servers

Alternatives to snapmaker-u1-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • 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.
      79 PyPI
      1
      MIT
    • 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
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to slice 3D models (STL files) headlessly using UltiMaker Cura's CuraEngine, returning ready-to-print G-code and estimated print time.
      12
      AGPL 3.0
    • A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to drive PrusaSlicer through MCP: select profiles, manage bed models, slice with verified settings, analyze G-code and print risks, and upload or control prints on networked printers.
      33
      AGPL 3.0

    TDQS

    C2.7/5.0

    Scored across 33 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, such as render_preview vs render_preview_bundle and compare_slices vs compare_orientations. A few potential overlaps exist (e.g., inspect_model vs diagnose_model, mesh_printability vs orientation_preflight) but they address different aspects, so ambiguity is low overall.

    Naming Consistency4/5

    All tools share the u1_ prefix and use snake_case. Most follow a verb_noun pattern (e.g., list_models, get_profile, export_run_report), though a few like 'health', 'profile_source_chain', and 'mesh_printability' are noun phrases. This deviation is minor and the naming remains predictable.

    Tool Count2/5

    With 33 tools, the surface is large and feels heavy. Many are variations on similar themes (e.g., three compare tools, two render preview tools, and extensive run management), suggesting some consolidation could reduce the count without losing functionality. The domain is complex, but this exceeds the typical well-scoped range.

    Completeness4/5

    The tool set covers the full slicing workflow: model inspection, profile management, slicing, run tracking, comparisons, transformations, diagnostics, and preview rendering. Minor gaps exist (e.g., no profile editing or model upload), but the core lifecycle is well-supported and no critical dead ends are apparent.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues