orcaslicer-mcp — Claude Code MCP server: features and setup
Connect an AI agent to a running OrcaSlicer to edit settings, prepare models, and inspect slicing results. Useful when print trade-offs need a closer look.
claude mcp add --env ORCA_API_TOKEN=<ORCA_API_TOKEN> --env ORCA_API_URL=<ORCA_API_URL> --env ORCA_MCP_ALLOW_KEYS=<ORCA_MCP_ALLOW_KEYS> --env ORCA_PRINTER_URL=<ORCA_PRINTER_URL> --env ORCA_PRINTER_API_KEY=<ORCA_PRINTER_API_KEY> --transport stdio orcaslicer-mcp -- uvx orcaslicer-mcpWhat orcaslicer-mcp does
The server works with an open OrcaSlicer session. An agent can load and arrange models, change settings, start a slice, and inspect time, filament use, and flow by print feature. It can also compare named setting variants and check a profile against printer limits using flow, temperature, geometry, and cooling calculations. OrcaSlicer must be running.
An offline reference provides setting labels, tooltips, types, ranges, and defaults from OrcaSlicer. On multi-filament setups, choosing a preset discards unsaved overrides across all groups, so edit filament settings before print settings. Printer tools make read-only requests; they do not send commands to the printer.
What it helps with
- identify which print features take the most time
- compare layer-height variants by time and filament use
- look up OrcaSlicer settings and their valid ranges
- check a profile against printer flow and geometry limits
- arrange a model and start slicing
Example prompts for the agent
- Show which features account for most of this model's print time.
- Compare these layer-height options by print time, filament use, and warnings.
- Check this profile against the printer's physical limits before slicing.
How to install orcaslicer-mcp
Platform CLI
claude mcp add --env ORCA_API_TOKEN=<ORCA_API_TOKEN> --env ORCA_API_URL=<ORCA_API_URL> --env ORCA_MCP_ALLOW_KEYS=<ORCA_MCP_ALLOW_KEYS> --env ORCA_PRINTER_URL=<ORCA_PRINTER_URL> --env ORCA_PRINTER_API_KEY=<ORCA_PRINTER_API_KEY> --transport stdio orcaslicer-mcp -- uvx orcaslicer-mcpReplace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from orcaslicer-mcp <command>
Platform CLI
codex mcp add orcaslicer-mcp --env ORCA_API_TOKEN=<ORCA_API_TOKEN> --env ORCA_API_URL=<ORCA_API_URL> --env ORCA_MCP_ALLOW_KEYS=<ORCA_MCP_ALLOW_KEYS> --env ORCA_PRINTER_URL=<ORCA_PRINTER_URL> --env ORCA_PRINTER_API_KEY=<ORCA_PRINTER_API_KEY> -- uvx orcaslicer-mcpReplace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from orcaslicer-mcp <command>
Config file
{
"mcpServers": {
"orcaslicer-mcp": {
"command": "uvx",
"args": [
"orcaslicer-mcp"
],
"env": {
"ORCA_API_TOKEN": "<ORCA_API_TOKEN>",
"ORCA_API_URL": "<ORCA_API_URL>",
"ORCA_MCP_ALLOW_KEYS": "<ORCA_MCP_ALLOW_KEYS>",
"ORCA_PRINTER_URL": "<ORCA_PRINTER_URL>",
"ORCA_PRINTER_API_KEY": "<ORCA_PRINTER_API_KEY>"
}
}
}
}Replace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from orcaslicer-mcp <command>
Config file
{
"servers": {
"orcaslicer-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"orcaslicer-mcp"
],
"env": {
"ORCA_API_TOKEN": "<ORCA_API_TOKEN>",
"ORCA_API_URL": "<ORCA_API_URL>",
"ORCA_MCP_ALLOW_KEYS": "<ORCA_MCP_ALLOW_KEYS>",
"ORCA_PRINTER_URL": "<ORCA_PRINTER_URL>",
"ORCA_PRINTER_API_KEY": "<ORCA_PRINTER_API_KEY>"
}
}
}
}Replace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from orcaslicer-mcp <command>
Platform CLI
gemini mcp add -e ORCA_API_TOKEN=<ORCA_API_TOKEN> -e ORCA_API_URL=<ORCA_API_URL> -e ORCA_MCP_ALLOW_KEYS=<ORCA_MCP_ALLOW_KEYS> -e ORCA_PRINTER_URL=<ORCA_PRINTER_URL> -e ORCA_PRINTER_API_KEY=<ORCA_PRINTER_API_KEY> orcaslicer-mcp uvx orcaslicer-mcpReplace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from orcaslicer-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about orcaslicer-mcp
How do I install orcaslicer-mcp in Claude Code?
Run claude mcp add orcaslicer-mcp -e ORCA_API_TOKEN=<ORCA_API_TOKEN> -e ORCA_PRINTER_API_KEY=<ORCA_PRINTER_API_KEY> -- uvx orcaslicer-mcp. This adds the MCP server; OrcaSlicer needs to be running.
What does orcaslicer-mcp do?
It lets an agent work with models and settings in OrcaSlicer, run slices, and inspect results such as print time and filament use by feature.
Does orcaslicer-mcp control the printer?
Its printer tools make read-only requests and do not send commands. The server connects to a running OrcaSlicer session.
