Skip to main content
Glama
akashnaren

bambu-mcp

by akashnaren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to bambu-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • OrcaSlicer MCP

      ShreddyKrueger75
      A
      license
      A
      quality
      A
      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
      2
      MIT

    • Bambu Printer MCP

      ceweldy
      A
      license
      B
      quality
      C
      maintenance
      Manages, monitors, slices for, and controls multiple Bambu Lab 3D printers with a privacy-focused multi-printer registry and fleet status.
      46
      GPL 2.0

    • Bambu Lab MCP Server

      schwarztim
      A
      license
      A
      quality
      B
      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
      26 npm
      19
      MIT

    • mcp-bambu

      billford
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to see and drive Bambu Lab 3D printers over the local network via MQTT, providing status, file management, print control, filament, maintenance, and diagnosis without any cloud dependency.
      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.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: slicing, file management, upload, print control, and separate read-only status queries. Even pause and stop are clearly differentiated by resumability.

    Naming Consistency3/5

    Tool names are readable and all lowercase, but they mix bare verbs (stop, upload, print), noun-style readouts (status, temps, ams), and compound snake_case names (slice_hook, list_files). The pattern is understandable but not uniform.

    Tool Count5/5

    Ten tools is a well-scoped count for a printer control server. Each tool covers a meaningful part of the workflow without redundancy or unnecessary surface area.

    Completeness4/5

    The core workflow of slicing, uploading, listing, printing, and controlling prints is well covered. Minor gaps like file deletion or temperature setting exist, but agents can complete the primary intended tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources