A
licenseNot graded
qualityB
maintenanceWraps the OrcaSlicer CLI to enable AI agents to slice 3D models, run parameter sweeps, and analyze G-code.
12 PyPI
1
MIT
orcaslicer-mcp
by MaxEllis
Related Servers
Alternatives to orcaslicer-mcp
Related Servers
- FlicenseAqualityCmaintenanceAn 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.122-
- FlicenseNot gradedqualityDmaintenanceMCP server that lets Claude Code dispatch tasks to the LiteLLM gateway, supporting both local Ollama models and Anthropic models via the gateway.-
- AlicenseAqualityBmaintenanceMCP server to dynamically load Claude Code skills into AI agents552 npm14MIT
- 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
- AlicenseNot gradedqualityAmaintenanceMCP server that enables Claude to control your computer, similar to Anthropic's computer use but easy to set up locally.1,112 npm379MIT
TDQS
A4.4/5.0
Scored across 44 tools
Disambiguation5/5
Despite a high tool count, each tool has a clearly distinct purpose. Slice-related tools are separated by blocking/non-blocking, single vs. multiple variants, and state vs. warnings vs. breakdown. Preset and object tools also have non-overlapping roles, with detailed descriptions preventing confusion.
Naming Consistency5/5
All tool names follow a consistent verb_phrase pattern in snake_case (e.g., list_presets, get_slice_status, transform_object). Even compound verbs like slice_and_wait and apply_and_slice fit the pattern, making the API predictable and easy to navigate.
Tool Count4/5
At 44 tools, this is a large set, but the complexity of OrcaSlicer's feature surface justifies the number. Each tool addresses a specific need across presets, slicing, object manipulation, and analysis. A few conveniences (apply_and_slice, compare_slices) could arguably be merged, but they offer clear utility, so the count is slightly over typical but reasonable.
Completeness5/5
The tool surface covers the full slicer workflow: loading and arranging models, managing presets and settings, slicing with various modes, inspecting results via stats, warnings, breakdowns, and visual rendering, and even recalling historical print outcomes. There are no obvious dead ends; every step from model to validated slice is supported.
Maintenance
ActivityActive
ResponsivenessSlow