Skip to main content
Glama
welingtonmatos

Bambu Studio MCP

by welingtonmatos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Bambu Studio MCP

No user-submitted related servers found.

    Related Servers

    • Laminador Bambu

      sebastian73m
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables slicing 3MF projects with a local Bambu Studio installation and exploring the resulting toolpaths, layers, print times, and filament usage in an interactive 3D viewer inside ChatGPT.
      AGPL 3.0

    • 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.
      66 PyPI
      1
      MIT

    • cura-mcp

      MichaelGagnon13
      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

    • 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

    A3.6/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (analysis, painting, environment, presets). The three slicing tools (slice_model, slice_project, compare_slices) share the core 'slice' action but are differentiated by input source and whether output is saved, so confusion is limited to a single family.

    Naming Consistency5/5

    All eleven tools follow a consistent snake_case verb_noun pattern (list_object_types, analyze_model, slice_model, get_settings, etc.). No mixed conventions or stylistic drift.

    Tool Count5/5

    Eleven tools is well within the ideal 3-15 range for a headless slicer service. Each tool covers a distinct capability (discovery, analysis, slicing, comparison, painting, validation) with no filler.

    Completeness4/5

    The surface covers the full discover-analyze-slice-verify lifecycle: resource listing, geometry analysis, slicing (model and project), variation comparison, painting, environment introspection and self-test. Actual printing is intentionally excluded, and export/preview handling is adequate, leaving only minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources