Skip to main content
Glama
SyJarvis

Bambuddy MCP Server

by SyJarvis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Bambuddy MCP Server

No user-submitted related servers found.

    Related Servers

    • bambu-gateway-mcp

      leolobato
      F
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to control Bambu Lab 3D printers via the bambu-gateway HTTP API, supporting printer listing, filament management, print session creation, and safe print initiation with user confirmation.
      7
      -

    • 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

    • 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

    • 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

    • MCP 3D Printer Server

      DMontgomery40
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with 3D printer management systems through an MCP server, supporting STL file manipulation, slicing, and control of printers like OctoPrint, Klipper, Duet, and more.
      57 npm
      236
      GPL 2.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

    A4.1/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, such as camera snapshot versus camera status or list printers versus diagnose printer. The only mild overlap is between get_printer_status and get_current_print, since both could reasonably be used to check ongoing print progress.

    Naming Consistency5/5

    Every tool follows the same bambuddy_<verb>_<noun> snake_case pattern with verbs like get, list, prepare, start, and diagnose. This makes the API surface highly predictable and easy for an agent to navigate.

    Tool Count5/5

    Nine tools is well within the ideal range and each tool serves a meaningful part of the printer monitoring and print-starting workflow. No tool feels redundant or unnecessary.

    Completeness4/5

    The core read-only monitoring, camera access, and safe print-start workflow are well covered, including preflight token handling. Minor lifecycle gaps exist, such as no cancel, pause, or print queue management tools, but the available surface supports the apparent primary use case.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources