SlicerBridge
Related Servers
Alternatives to SlicerBridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to prepare and inspect STL/3MF files and run offline slicing on an isolated Windows desktop while leaving the mouse, keyboard, and visible desktop usable; also supports an X2D dual-nozzle workflow with offline validation of sliced 3MF archives and nozzle assignments.GPL 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to work with OrcaSlicer code and perform slicing operations, such as reading files, checking Git status, and slicing 3D models to get print time and filament usage.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI hosts to interact with a browser CAD workbench through model-neutral local stdio or authenticated remote MCP tools, supporting command discovery, design-health analysis, and scoped previews while never reading local files or taking over open sessions.MIT
- AlicenseCqualityBmaintenanceEnables AI assistants to drive PrusaSlicer through MCP: select profiles, manage bed models, slice with verified settings, analyze G-code and print risks, and upload or control prints on networked printers.33AGPL 3.0
- AlicenseCqualityBmaintenanceConnects an AI assistant to a running SOLIDWORKS session to build and inspect native models, validate explicit design requirements, compare isolated part variants, and generate native Visualize product-shot packs with measurable artifacts.123MIT
- AlicenseAqualityCmaintenanceEnables LLM clients to slice, paint, and verify 3D prints through the installed slicer's command line for any installed Bambu printer, nozzle, and filament, with settings per object type. It never sends jobs to a printer.11MIT
TDQS
Scored across 6 tools
Most tools target a clearly distinct phase of the workflow: list_printers (discovery), inspect_model (input analysis), convert_model (output writing), doctor (environment diagnostics). brand_check and verify_files both revolve around checking/slicing files, which could cause occasional misselection, though the descriptions distinguish third-party slicer comparison from re-validating SlicerBridge's own output.
Five of six tools follow a clean verb_noun snake_case pattern (brand_check, verify_files, list_printers, convert_model, inspect_model). 'doctor' is a bare noun diagnostic command, a minor deviation from the otherwise consistent convention.
Six tools is well-scoped for a slicer bridge: discovery, inspection, conversion, verification, brand comparison, and diagnostics each earn a distinct place. Nothing feels padded or missing at this count.
The core lifecycle is covered: list printers, inspect a model, convert it, then verify the written files, with doctor and brand_check as supporting operations. Minor gaps exist around managing/registering printers or templates and cleaning up old outputs, but agents can work around these for the stated purpose.