No user-submitted related servers found.
Scored across 21 tools
Most tools map to a distinct resource+action: mesh transforms (scale/rotate/extend/merge/center/lay_flat), inspection (get_stl_info, list_3mf_plate_objects, get_slice_settings), slicing and knowledge lookup are all clearly separated. The main overlaps are slice_stl vs slice_with_template (the latter is explicitly documented as a wrapper) and the Blender trio, where blender_mcp_call is generic while blender_mcp_edit_model is a specific workflow — an agent could pick the generic call when the specialized one is intended. Descriptions are detailed enough that these are manageable confusions rather than true ambiguity.
All names are snake_case and almost all follow verb_noun (scale_stl, save_template, consult_knowledge, center_model). A few break the pattern with noun-only or adjective-only names (slicer_info, preflight_check, lay_flat), and the blender_mcp_ prefix group signals a subsystem rather than a verb convention. Readable and predictable overall, with minor deviations.
At 21 tools the surface is on the heavy side, spanning three subsystems: STL geometry edits, Bambu Studio slicing/project workflow, and a Blender bridge. Each tool does appear to earn its place, but the count sits in the 16-25 band where scope starts to feel broad for a single server. Consolidating the Blender trio or the templating pair would tighten it.
The lifecycle is well covered: inspect a part, transform it, preflight it against rules, slice, prepare a tuned project, save/reuse templates, and open results in the GUI, plus a Blender escape hatch. Gaps are minor: the template registry has list/save but no delete or update, and there is no translation/move tool or G-code inspection tool. Agents can work around these.