Skip to main content
Glama
selcukgk29

bambu-sentinel-mcp

by selcukgk29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to bambu-sentinel-mcp

No user-submitted related servers found.

    Related Servers

    • bambu-mcp

      akashnaren
      A
      license
      A
      quality
      B
      maintenance
      Enables LAN-based monitoring and control of Bambu Lab P2S/P1S printers, including confirm-gated print, pause, resume, stop, file upload, and slicing workflows.
      10
      18 npm
      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

    • 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

    • BambuStudio MCP Server

      hunter-stradley
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides end-to-end 3D printing automation for Bambu Lab printers, allowing users to generate, slice, and monitor prints using natural language. It features model generation from text or images, real-time camera monitoring, and automated print quality improvement.
      MIT

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

    B3.2/5.0

    Scored across 48 tools

    Disambiguation4/5

    Tools are mostly distinct and organized into clear domain families such as queue_, spool_, hms_, workshop_, and cost_, so an agent can usually select correctly. Minor overlap remains around plate-clearing/ejection (confirm_plate_cleared, save_empty_plate_reference, eject_plate) and monitoring (get_snapshot, inspect_print, get_events), but the descriptions differentiate them well.

    Naming Consistency4/5

    Names consistently use snake_case with domain prefixes, which makes the set readable and predictable. However, ordering alternates between noun_verb forms like queue_list, printer_status, and hms_active and verb_noun forms like add_printer, set_light, and estimate_cost, so it is not a single uniform pattern.

    Tool Count2/5

    At 48 tools, this server is far beyond the typical well-scoped range of 3-15 and falls into the 25+ heavy category. Each tool may be useful, but the large surface increases selection burden and would benefit from consolidation or splitting into sub-servers.

    Completeness5/5

    Coverage is unusually complete across printers, queue management, spool tracking, cost analysis, history, HMS errors, camera supervision, plate ejection, and workshops. Core lifecycle operations and configuration are present, with no obvious missing CRUD or workflow gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources