orca-profiles-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORCA_USER_DIR | No | Path to the OrcaSlicer user profile directory when the default tree is not used (e.g. "$HOME/Library/Application Support/OrcaSlicer/user/default") |
Instructions
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_setupB | Discovered Orca profile roots, application version, vendors, selected presets |
| list_profilesC | Search profiles by type, name, vendor and source |
| 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 |
| get_chainC | The inheritance chain to its root, with how each link was resolved |
| explain_keyB | Where a key's value came from: originating link, overridden values, engine default |
| find_childrenC | Profiles inheriting from this one. Check before editing shared profiles |
| diff_profilesB | Compare two profiles by effective values (mode=resolved) or by their stored deltas (mode=raw) |
| validateC | Integrity check: broken inherits, cycles, unknown keys, redundant deltas, name collisions |
| check_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 |
| compare_with_upstreamC | Compare a profile against its version in the OrcaSlicer repository |
| 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 |
| create_profileC | Create a user profile inheriting from the given one |
| rename_profileC | Rename a user profile |
| delete_profileB | Delete a profile; deleting outside your own profiles needs force=True, and cloud-synced ones keep a flagged .info |
| normalize_profileC | Drop keys whose values are identical to the parent's |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.