orca-profiles-mcp
This server is an MCP interface for reading, inspecting, and editing OrcaSlicer profiles with full inheritance resolution and provenance tracking.
Discover environment:
get_setupreports profile roots, Orca version, vendors, and selected presets.Search profiles:
list_profilesfilters by type, name, vendor, source, compatibility, and abstract status.Read profiles:
get_profilereturns raw file contents, resolved effective values, or traced values with provenance;get_chainshows the inheritance chain;explain_keytraces where a specific value came from.Find dependents:
find_childrenlists profiles that inherit from a given profile.Compare profiles:
diff_profilescompares effective values or stored deltas;compare_with_upstreamcompares against the OrcaSlicer repository.Validate integrity:
validatechecks broken inherits, cycles, unknown keys, redundant deltas, and name collisions;check_deltasverifies expansion against deltas Orca itself wrote.Edit profiles:
set_valuesupdates values with automatic delta recomputation;create_profilecreates user profiles;rename_profileanddelete_profilemanage profiles;normalize_profiledrops keys identical to the parent.Safety controls: system/bundled profile edits require
force=true; writes are atomic with optional backups and type/value validation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@orca-profiles-mcp Trace where my outer wall speed value comes from in my current PLA profile."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
orca-profiles-mcp
An MCP server that reads and edits OrcaSlicer profiles. It expands the whole
inherits chain and shows which link set every value.
What it does
An OrcaSlicer profile stores only its differences from its parent. Opening the file is not enough to learn the outer wall speed: the value may come from the parent, from the parent's parent, or from the engine's built-in defaults. This server walks the chain to its root, computes the effective values and keeps their provenance.
It handles the parts of Orca that break naive readers:
parents are resolved by name, across vendors — a Sovol filament inherits from the OrcaFilamentLibrary;
a missing
Generic …parent falls back toGeneric <material> @System, and renamed profiles are found through theirrenamed_fromlist;vectors bound to extruder variants merge element by element, including the
nilmarker that means "keep the parent's value here";a child may declare more extruders than its parent — a toolchanger on top of a single-extruder machine profile — and both extruders keep their values;
keys that do not belong to the profile's type are dropped, because Orca drops them too; they are reported instead of being silently applied.
Related MCP server: obsidian-cli-mcp
Setup
cd ~/job/orca-profiles-mcp
uv syncRegister with Claude Code:
claude mcp add orca-profiles -- uv --directory ~/job/orca-profiles-mcp run orca-profiles-mcpTools
Tool | Purpose |
| discovered roots, Orca version, vendors, selected presets |
| search by type, name, vendor, source |
| profile in |
| inheritance chain to the root |
| where a specific value came from |
| which profiles inherit from this one |
| compare two profiles |
| compare against the OrcaSlicer repository |
| broken |
| verify expansion against the deltas Orca itself wrote |
reports redundant keys and unexplained vector lengths separately | |
| set values with delta recomputation |
| create a user profile |
| rename and delete |
| drop keys identical to the parent's |
Values are returned exactly as the files store them: "0.20" stays "0.20",
and "100%" stays a percentage. The engine normalises both when it slices;
this server does not, so what you read is what the profile says and what gets
written back is unchanged.
Which profile tree it reads
Orca keeps one profile tree per signed-in account under user/<account-id>,
and writes into user/default when signed out. Its config records neither, so
when both exist the server picks the most recently written one and says so in
get_setup and in every write report. If profiles you create do not show up in
the application, you are on the other tree — point ORCA_USER_DIR at it:
ORCA_USER_DIR="$HOME/Library/Application Support/OrcaSlicer/user/default"Sync backups in dot-directories (.sync_bak) are ignored; they are copies, not
live profiles.
Writing profiles
Your own profiles are edited freely. Touching a system or bundled one requires
force=true: those files belong to a vendor library, the next profile update
restores them, and every descendant inherits the change.
Writes go through a temporary file and an atomic rename, so an interrupted
write cannot truncate a profile, and a backup copy is made next to the file
first (backup=false disables it). Values are checked before anything is
written — a key belonging to another profile type, a vector where the engine
wants a scalar, or a number where the format requires a string is refused
rather than stored and silently dropped by Orca. Settings your pinned snapshot
does not recognise are carried through untouched, so a profile written by a
newer Orca does not lose them.
OrcaSlicer reads profiles at startup and rewrites them at exit. Edits made while the application is running will be overwritten — close Orca first.
How correctness is checked
Orca's CLI cannot verify inheritance. --export-settings returns the engine
defaults plus the keys present in the files handed to it and never walks
inherits; selecting presets through OrcaSlicer.conf does not activate them;
passing a whole chain as a file list is rejected as a duplicate config file.
All three were tried against 2.4.2.
What Orca does leave behind is evidence of its own expansion: when it saves a
user profile it stores the minimal delta against the fully expanded parent. So
every profile Orca has written is a recorded answer. check_deltas recomputes
those deltas and compares — a mismatch means the resolver expands a parent
differently than the engine did.
This is what tests/test_smoke.py asserts against the installed library, and
it is how the toolchanger vector defect was found.
Keys stored despite already matching the parent are reported separately: they are harmless leftovers from before a parent changed, not resolver errors.
Refreshing the engine snapshot
Engine defaults, the variant key sets and the per-type key lists are captured
from the installed Orca into src/orca_profiles_mcp/data/engine-snapshot.json,
pinned to its version tag. After upgrading OrcaSlicer:
uv run python scripts/build_snapshot.py
uv run pytestTests
uv run pytestFour layers:
unit tests over a miniature fixture library, one per edge case — cross-vendor inheritance, the
Genericfallback,renamed_from, cycles, missing parents, stride-1 and stride-2 vectors,nilelements;write round-trips: read → write unchanged → the file is byte-identical;
end-to-end tests that spawn the packaged entry point as a subprocess and drive it over MCP stdio, covering tool registration, a full create/edit/verify/delete cycle, and error propagation;
checks against the installed library, including the delta verification described above.
Tests using the real library skip themselves when no Orca data directory is present; everything else runs against fixtures.
Documents
Design:
docs/specs/2026-08-17-orca-profiles-mcp-design.md— includes what reading the OrcaSlicer sources established about the profile format, and what the CLI experiments ruled outImplementation plan:
docs/plans/2026-08-17-orca-profiles-mcp.md
Licence
AGPL-3.0, matching OrcaSlicer itself.
This project contains no OrcaSlicer code, but its inheritance logic is a
line-by-line port of Preset.cpp and PrintConfig.cpp, and the engine snapshot
holds default values and key lists extracted from that source.
Not affiliated with or endorsed by the OrcaSlicer project.
Available Tools
15 toolscheck_deltasB
Verify inheritance expansion against the deltas Orca itself wrote: for every profile, the delta is recomputed and compared with the file. A mismatch means the resolver expands the parent differently than the engine did; redundant keys are reported separately and are harmless
Inputs: scope.
compare_with_upstreamC
Compare a profile against its version in the OrcaSlicer repository
Inputs: name (required), type (required), ref.
create_profileC
Create a user profile inheriting from the given one
Inputs: name (required), type (required), values (required), inherits (required).
delete_profileB
Delete a profile; deleting outside your own profiles needs force=True, and cloud-synced ones keep a flagged .info
Inputs: name (required), type (required), force.
diff_profilesB
Compare two profiles by effective values (mode=resolved) or by their stored deltas (mode=raw)
Inputs: a (required), b (required), type (required), mode.
explain_keyB
Where a key's value came from: originating link, overridden values, engine default
Inputs: key (required), name (required), type (required).
find_childrenC
Profiles inheriting from this one. Check before editing shared profiles
Inputs: name (required), type (required).
get_chainC
The inheritance chain to its root, with how each link was resolved
Inputs: name (required), type (required).
get_profileC
A profile with inheritance expanded. mode: raw — file contents, resolved — effective values, traced — values with provenance. Engine defaults are excluded unless include_defaults is set
Inputs: name (required), type (required), keys, mode, +3 more.
get_setupB
Discovered Orca profile roots, application version, vendors, selected presets
Inputs: no named parameters.
list_profilesC
Search profiles by type, name, vendor and source
Inputs: type, limit, query, source, +3 more.
normalize_profileC
Drop keys whose values are identical to the parent's
Inputs: name (required), type (required), force, backup.
rename_profileC
Rename a user profile
Inputs: name (required), type (required), new_name (required).
set_valuesA
Set profile values. The delta against the parent is recomputed automatically and the paired .info is updated. Editing a system or bundled profile affects every descendant and needs force=True
Inputs: name (required), type (required), values (required), force, +1 more.
validateC
Integrity check: broken inherits, cycles, unknown keys, redundant deltas, name collisions
Inputs: scope.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes: get_profile expands inheritance, get_chain shows the chain, explain_key traces a single key's origin. However, validate and check_deltas both verify integrity and could be confused; diff_profiles and compare_with_upstream both compare but to different targets. Descriptions are detailed enough to resolve ambiguity.
All tool names follow a consistent snake_case imperative verb-noun pattern (get_setup, list_profiles, set_values, create_profile). Even compound names like compare_with_upstream and check_deltas fit the pattern. No mixed conventions or vague verbs.
15 tools is well-scoped for a profile management server, covering discovery, inspection, mutation, validation, and comparison. Each tool addresses a distinct need without unnecessary duplication.
The tool surface provides full lifecycle coverage: create, read (multiple views), update, delete, rename, plus validation, diffing, and impact analysis (find_children). Missing operations like import/export are not core to the domain, and the set appears complete for effective profile management.
Related MCP Connectors
MCP server for progressive tool usage at any scale (see https://klavis.ai)
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
MCP Server for Slima - AI Writing IDE for Novel Authors with AI Beta Reader.
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server for interactively reading, validating, previewing, and saving Renovate configurations with LLM assistance.1,018 npm13MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the Obsidian CLI with controlled profiles for governed read-only and mutation operations, plus a personal-unrestricted profile for full access.12 npmAGPL 3.0
- FlicenseNot gradedqualityDmaintenanceProfile-driven MCP server for safely inspecting and changing local Git repositories via a Streamable HTTP endpoint with deny-by-default security.1-
- AlicenseNot gradedqualityDmaintenanceMCP server for pre-print QA of Bambu Studio projects, providing tools to inspect models and 3MF files, validate risky settings, create support variants, and open files in Bambu Studio.MIT