bambu-printer-mcp
Related Servers
Alternatives to bambu-printer-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for pre-print QA of Bambu Studio projects, providing tools to inspect models and 3MF files, validate risky settings, create support variants, and open files in Bambu Studio.-
- AlicenseBqualityDmaintenanceAn MCP server for controlling Bambu Lab 3D printers that enables users to manipulate STL files, slice 3MF files, and manage end-to-end print workflows directly from Claude. It provides real-time status monitoring, file management via FTPS, and printer control through MQTT for a focused, lean Bambu-only implementation.4186 npm128GPL 2.0
- FlicenseNot gradedqualityBmaintenanceAn 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.22-
- AlicenseNot gradedqualityFmaintenance3D Printing MCP By OctoEverywhere36Apache 2.0
- FlicenseAqualityCmaintenanceEnables remote cloud control and live LAN camera access for Bambu Lab 3D printers through 31 MCP tools.31-
- AlicenseAqualityCmaintenanceEnables MCP clients to monitor and control a Bambu Lab P1S printer over the local network, including status, file management, slicing, and print operations.11MIT
TDQS
Scored across 37 tools
Most tools have clearly distinct purposes, with specific actions for STL editing, printer control, file management, and slicing. However, some overlap exists between upload_file and upload_gcode, and between slice_stl and slice_with_template, which could cause minor ambiguity.
The overwhelming majority of tool names follow a consistent verb_noun pattern in snake_case (e.g., cancel_print, get_printer_status, set_temperature). Only a few deviate slightly (camera_snapshot, lay_flat), but the pattern is clear and predictable.
With 37 tools, the server exceeds the typical well-scoped range of 3-15 and falls into the 'too many' category. While the features cover a broad scope (STL editing, slicing, printing, AMS control), the sheer number can be overwhelming and suggests some tools could be split into separate servers.
The tool set covers many aspects of the printing workflow, including file management, slicing, printing, and printer control. However, there are notable gaps such as explicit filament load/unload, bed leveling, and detailed print progress monitoring, which agents may need to work around.