Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to bambu-printer-mcp

No user-submitted related servers found.

    Related Servers

    • bambu-printer-mcp

      rowbotik
      A
      license
      B
      quality
      C
      maintenance
      A Bambu Lab-focused MCP server for controlling Bambu printers, manipulating STL files, and managing end-to-end 3MF print workflows from any MCP-compatible client.
      37
      117 npm
      1
      GPL 2.0

    • 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

    • Bambu Lab MCP Server

      schwarztim
      A
      license
      A
      quality
      D
      maintenance
      Enables comprehensive control and monitoring of Bambu Lab 3D printers through Claude using local MQTT, FTPS, and X.509 authentication. Users can manage print jobs, monitor real-time status, handle filament through AMS, and adjust hardware settings like temperature and lighting.
      24
      21 npm
      22
      MIT

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

    • bambu-p1s-mcp

      marctheshark3
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to monitor and control a Bambu Lab P1S printer over the local network, including status, file management, slicing, and print operations.
      11
      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.2/5.0

    Scored across 45 tools

    Disambiguation3/5

    Several tools have overlapping purposes: start_print and start_print_job are aliases, slice_stl and slice_with_template are related, and print_3mf vs print_3mf_bambu_network target different paths. Descriptions clarify most distinctions, but an agent still faces non-trivial misselection risk.

    Naming Consistency4/5

    The set is predominantly snake_case and action-oriented, with predictable names like get_printer_status, upload_file, and set_temperature. Minor deviations such as camera_snapshot (noun phrase) and skip_objects (verb-only) exist but do not break readability.

    Tool Count2/5

    At 45 tools, the server is heavily over-provisioned for a printer-control MCP. Many specialized and overlapping operations could be consolidated, making the surface harder to navigate than necessary.

    Completeness3/5

    Core lifecycle coverage exists for file management, printing, slicing, and AMS inspection, but notable gaps remain. There is no explicit filament load/unload tool despite get_printer_filaments recommending load_filaments, and calibration start is absent from x2d_native_control.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources