A
licenseNot graded
qualityC
maintenanceWraps the OrcaSlicer CLI to enable AI agents to slice 3D models, run parameter sweeps, and analyze G-code.
68 PyPI
1
MIT
orcaslicer-mcp
by MaxEllis
Related Servers
Alternatives to orcaslicer-mcp
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server that drives OrcaSlicer headlessly on a virtual display, enabling an agent to import 3D models, slice them, and export G-code without a physical screen or GUI automation.124-
- AlicenseBqualityAmaintenanceMCP server for BambuStudio slicer: inspect geometry, configure saved projects, and compare slices with Claude Code or Codex.192AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceMCP server that lets Claude Code dispatch tasks to the LiteLLM gateway, supporting both local Ollama models and Anthropic models via the gateway.-
- AlicenseAqualityAmaintenanceMCP server to dynamically load Claude Code skills into AI agents576 npm15MIT
- AlicenseNot gradedqualityFmaintenanceA simple MCP server that enables Claude to communicate with locally running LLM models via LM Studio.9MIT
- AlicenseAqualityCmaintenanceA self-hosted MCP server that lets Claude (or any MCP client) drive Autodesk Fusion 360 on your own machine.982MIT
TDQS
A4/5.0
Scored across 53 tools
Disambiguation4/5
Descriptions are unusually thorough and explicitly cross-reference alternatives ('use X instead of Y'), which makes even near-neighbors like slice/slice_and_wait/apply_and_slice and compare_settings/compare_slices separable. A few genuine overlaps remain: find_config_keys vs search_settings, check_placement vs diagnose_plate, and recall_prints vs list_print_history, but the docs largely disambiguate them.
Naming Consistency4/5
The set is almost entirely consistent snake_case verb_noun (get_status, set_config, list_plates, delete_preset). Minor deviations are a handful of bare verbs/adjectives like consult, remember, and recall_prints, but nothing that breaks the pattern.
Tool Count2/5
53 tools is far beyond the 3-15 sweet spot and well past the 25+ 'heavy' threshold. The domain (slicing, presets, objects, plates, printer monitoring, outcomes, diagnostics) is broad, but the surface is bloated with many overlapping convenience variants (slice, slice_and_wait, apply_and_slice, compare_settings, compare_slices, get_slice_status, get_slice_warnings, get_slice_breakdown).
Completeness5/5
Coverage is exhaustive: full CRUD for objects, plates, and presets, config read/write, multiple slicing paths, G-code save/render/describe, printer status/history, physics and placement checks, and persistent memory. Lifecycle for every stated sub-domain appears closed with no obvious dead ends.
Maintenance
ActivityActive
ResponsivenessResponsive