Related Servers

Many tools are clearly distinct (camera_snapshot vs set_fan_speed vs merge_vertices), but several clusters overlap badly: start_print is documented as an alias of start_print_job, print_3mf vs print_3mf_bambu_network vs start_print_job vs bambu_connect_import_file all describe 'start printing'-adjacent flows, and upload_gcode vs upload_file vs inspect_print_file blur together. The one-off print_collar_charm and catch-all x2d_native_control add further ambiguity about when to prefer them.

The bulk of names follow a verb_noun snake_case pattern (slice_stl, set_light, list_printer_files, cancel_print), but there are noun-first outliers like x2d_native_control, bambu_network_bridge_status, and print_collar_charm, plus vendor-prefixed families (bambu_*, blender_mcp_*). Readable, but the convention is not predictable across the set.

46 tools is far beyond a well-scoped surface for this server; the set spans STL geometry ops, slicing, MQTT control, FTPS file management, Blender bridging, and BambuNetwork plumbing. Multiple tools exist only as compatibility aliases or single-use scripts (start_print, print_collar_charm), which inflates the count without adding capability.

Coverage of the printing domain is genuinely broad: geometry prep, slicing/templating, inspection, upload, lifecycle control (pause/resume/cancel/skip), AMS/filament, environment settings, and camera. Minor gaps remain — templates can be listed and saved but not deleted, and file deletion is restricted to cache/timelapse/logs with no general cleanup path — but agents have workarounds.