Schema | OrcaSlicer MCP Server

OrcaSlicer MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`workdir`	No	The directory that will serve as the working folder for projects and operations.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
list_profilesC	List available profile files for a given category (machine, filament, or process).
search_settingsA	Search for setting keys containing a keyword across all (or a specific type of) profiles. Useful when you don't know the exact key name — e.g. query "infill" returns all infill-related settings and their current values.
get_profile_contentB	Read and return the full JSON content of a profile file.
update_profile_settingA	Update a single setting key in a profile. By default (dry_run=true), the change is saved to a _tuned copy rather than overwriting the original.
slice_modelC	Run OrcaSlicer CLI to slice a model file. Specify input/output filenames and optionally profiles to use.
analyze_gcode_metadataB	Parse metadata (estimated time, filament usage, cost, layers) from a G-code file and return structured JSON.
health_checkB	Diagnose the server environment: check if the OrcaSlicer binary is reachable and if the settings/work directories are accessible.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/itsumonotakumi/orcaslicer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server