In-depth architectural comparison of the Orcaslicer MCP and Tracepass MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Orcaslicer MCP
Industrial & IoT · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Tracepass MCP Server
Industrial & IoT · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Orcaslicer MCP if you need specialized Industrial & IoT tools running via a local process. Choose Tracepass MCP Server if your workspace requires Industrial & IoT integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Orcaslicer MCP when:
You need dedicated capabilities in the Industrial & IoT domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Drive a running OrcaSlicer with AI: load models, tune settings, slice, and analyze results
EU Digital Product Passport automation for AI agents. Create products, build and audit DPPs (battery, electronics, textiles, and more), set economic-operator parties, and read or capture GS1 EPCIS 2.0 supply-chain events via the TracePass platform. 6 tools, hosted (https://ai.tracepass.eu/mcp) or local. Install via npx -y tracepass-mcp-server.
Category & Scope
Tools & Capabilities Breakdown
Orcaslicer MCP Tools (44)
get_status
Snapshot of the current OrcaSlicer session: app and project info, the active
print/filament/printer presets with which of their keys are modified (dirty), whether the
last slice is still valid, and whether a slice is running. Read-only.
Call it first to orient before slicing or editing, to see which settings drift from their
preset, or to check slice_result_valid before trusting earlier stats.
get_config
Read merged config values (optionally filtered to `keys`).
set_config
Apply config changes to the active project as unsaved overrides, atomically: if any
key is invalid the whole batch is rejected and nothing changes. Returns {applied, errors}.
Overrides show as modified in get_status, are not written to any preset file, and revert
if the preset is reselected; call save_preset to persist them. Each apply invalidates the
last slice, so re-slice afterwards. It does not run the physics gate, so for temperature,
speed, acceleration, or flow keys run check_profile_physics before trusting the result. To
edit a stored preset rather than the live project, use edit_preset.
slice
Start slicing the current plate in the background and return immediately, without waiting
for the result. The reply is 'started' (a slice began), 'already_valid' (the plate is
unchanged and the last result still holds), or a conflict if a slice is already running.
Fire-and-forget: poll get_slice_status for progress and stats, or cancel_slice to stop it.
Prefer slice_and_wait when you want the finished stats back in one call.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Orcaslicer MCP is categorized under Industrial & IoT and uses a local stdio subprocess. In contrast, Tracepass MCP Server belongs to Industrial & IoT using local stdio subprocess. Select Orcaslicer MCP when you need capabilities focused on industrial & iot and Tracepass MCP Server when you require tools for industrial & iot.
State of the current or most recent slice: state (slicing, done, error, or idle), stats
(print time and filament use when done), and any warnings or errors. Read-only.
Poll this after slice to follow progress and read the result; 'idle' means no slice has run
or it was cancelled. For only the pass/fail warnings use get_slice_warnings; for a
per-feature time and filament breakdown use get_slice_breakdown.
get_slice_warnings
Just the warnings/errors from the last (or current) slice, plus validity - the
fast 'did anything go wrong' check and the way to confirm a fix cleared.
NOTE: only as complete as the API exposes. On the current fork build this may report
valid with an empty warnings list even when the GUI shows a plate-boundary toast -
the fork must populate the plater warning list (tracked as the fork batch). Once it
does, this reports the real warnings with no change here.
get_slice_breakdown
Per-feature breakdown of the last slice + a stateless predicted-vs-observed flow check.
Returns per-role time/filament + speed/flow ranges, global time-weighted metric
distributions, per-layer aggregates, and a prediction_check flagging where the profile's
speed was silently throttled at the flow ceiling ('clamped'). Answers 'which feature is
the time hog' directly instead of by trial slicing.
Degrades to {"available": false, "reason": ...} on fork builds that don't emit the
breakdown, or when there is no valid slice.
cancel_slice
Abort a running slice, or unwedge a stale 'slicing' state (e.g. after an
object outside the bed). Safe when idle.
slice_and_wait
Slice the current plate and block until it finishes, then return the final stats and
warnings in one call. If the plate is already sliced and unchanged, it returns the existing
result without re-slicing.
This is the usual way to slice when you want the outcome immediately. For a non-blocking
start, use slice then poll get_slice_status; to sweep one setting across values, use
compare_settings.
apply_and_slice
Apply config overrides and then slice in one step, returning {applied, errors, result}
with the resulting stats and warnings. The changes are atomic (any invalid key rejects the
whole batch) and unsaved, exactly like set_config, so they revert if the preset is reselected.
Use this to test the effect of a tweak in a single call. Use set_config then slice_and_wait
to keep the steps separate, or compare_settings to try several values of one key.
compare_settings
For each value of `key`, slice and collect stats/warnings; restore the original when done.
Non-destructive: the original value of `key` is put back even on error.
compare_slices
Slice the current plate under several named variants and compare the cost of each.
Each variant is {"name": str, "changes": {setting: value}}; changes={} means the
current config as-is (a natural baseline row). Applies each variant over the ORIGINAL
config (resetting between variants, so they don't stack), slices it, then restores your
config exactly as it was - nothing is left changed (slice validity is left false, as
after any un-resliced edit).
Returns a ready-to-relay `headline` and `table_markdown`, plus structured `variants`.
All deltas and percentages are ALREADY computed and rounded against `baseline`
(defaults to the changes={} variant, else the first) - relay them as given rather than
recomputing. `recommended` names one pick; `recommended_is_dominant` says whether it
beats every variant on every axis (time, filament, warnings) or is only the fastest
warning-free option amid a genuine trade-off (`tradeoff` then names the frontier).
Each variant is a full slice (minutes); capped at 8. Set detail=True only when a
per-feature (wall/infill/support) split is wanted - it grows the response ~N x. With
more than ~5 variants, lead with the recommendation and the extremes, not all rows.
+32 more tools listed on main page
Tracepass MCP Server Tools (6)
tracepass_products
Manage the TracePass product catalogue. A product is the catalogue layer — one product can have many passports (one per serialised unit). Products are not billable on their own.
Actions (pass via `action`, with `args`):
- list — args: { page?, limit? (≤100), category?, status?, search? }. Read-only.
- get — args: { id }. Read-only.
- create — args: { name, model, category, description? }. `category` is one of: battery, textile, electronics, construction, steel, detergents, paints-coatings, packaging, furniture, tyres, jewelry, toys, fmcg.
- update — args: { id, name?, model?, description? }; pass at least one field to change.
- create_batch — args: { products: [ { name, model, category, description? }, … ] }, up to 100. Partial-success: the response carries a per-item status, so some items can be created while others error. The whole batch consumes N writes upfront; if that would exceed the daily cap NOTHING is created (429).
- archive — args: { id }. Soft-archive a product. Blocked with 409 while any non-archived passport still references it — archive those passports first. This is reversible and is NOT deletion.
tracepass_passports
Manage Digital Product Passports — create, read, and run lifecycle actions.
IMPORTANT: `create` consumes a DPP slot on the account's plan and IS BILLABLE. Creating a passport beyond the included quota incurs a per-passport overage charge; if over quota the tool returns a 402-style message — only re-run with args.confirmOverage=true after the user explicitly agrees to the charge. `archive` is IRREVERSIBLE (the public QR permanently 404s); prefer `suspend` when a change might be undone.
Actions (pass via `action`, with `args`):
- list — args: { page?, limit? (≤100), productId?, status?, search? }. status ∈ draft|in_review|approved|published|suspended|expired|archived. Read-only.
- get — args: { id, format? (summary|full), lang? }. Read-only.
- get_by_serial — args: { serial, format?, lang?, gtin? }. Read-only. Addresses the passport by your own serial. A serial is unique only WITHIN a GTIN — if the same serial exists under two GTINs in your account the call returns 409 ambiguous_serial; pass `gtin` (or use the by-id action) to resolve exactly.
- compliance — args: { id }. Read-only. Returns a three-tier compliance verdict (compliant | compliant_with_warnings | incomplete) with regulation-cited findings — use to gap-check a passport against the rules for its category, fix the cited fields/parties, then re-check.
- registry_readiness — args: { id }. Read-only. Returns { ready, findings[] } — whether the passport would pass the EU DPP Registry's FORMAL submission gate (mandatory fields present, correct formatting, a resolvable public link, item-level granularity via a serial number, and a well-formed commodity code where the category carries one). This is the registry's mechanical pre-submission check, NOT the substantive compliance verdict; a passport can be registry-ready yet not substantively compliant. Battery passports only.
- create — args: { productId, gtin, serialNumber, confirmOverage? }. BILLABLE.
- suspend — args: { id }. Reversible — public QR shows 'suspended'.
- suspend_by_serial — args: { serial, gtin? }. Same as suspend, addressed by your serial. 409 ambiguous_serial if the serial isn't unique in your account — pass `gtin`.
- archive — args: { id }. IRREVERSIBLE — confirm with the user first.
- archive_by_serial — args: { serial, gtin? }. IRREVERSIBLE, addressed by your serial — confirm first. 409 ambiguous_serial if the serial isn't unique — pass `gtin`.
- get_qr — args: { id, format? (svg|png) }. Read-only.
- get_qr_by_serial — args: { serial, format? (svg|png), gtin? }. Read-only. Same as get_qr, addressed by your own serial. A serial is unique only WITHIN a GTIN — if the same serial exists under two GTINs in your account the call returns 409 ambiguous_serial; pass `gtin` (or use get_qr by id) to resolve exactly.
tracepass_passport_fields
Update field values on a Digital Product Passport. Every change is recorded in the passport's audit trail, tagged as an API-key update.
Actions (pass via `action`, with `args`):
- update — args: { id, fieldKey, value }. `value` type matches the field's dataType (string, number, boolean, array, object).
- update_by_serial — args: { serial, fieldKey, value, gtin? }. Same as update, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in your account the call returns 409 ambiguous_serial; pass `gtin` (or use update by id) to resolve exactly.
tracepass_passport_parties
Manage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg. Each party carries a legal name and ideally a validated 13-digit GS1 GLN.
Actions (pass via `action`, with `args`):
- set — args: { id, role, legalName, gln?, country?, legacyOperatorId? }. Sets or updates one role.
- remove — args: { id, role }. Clears one role.
tracepass_epcis
GS1 EPCIS 2.0 supply-chain events. `export` is included on Starter plans and up; `capture`, `capture_job`, and `query` require the paid EPCIS add-on (those actions return a 403-style message without it).
Actions (pass via `action`, with `args`):
- export — args: { id }. Export a passport's events as an EPCIS 2.0 JSON-LD document. Read-only.
- export_by_serial — args: { serial, gtin? }. Same as export, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in your account the call returns 409 ambiguous_serial; pass `gtin` (or use export by id). Read-only.
- capture — args: { events }. `events` is an EPCISDocument, a single event, or an array of events (JSON-LD). Returns a 202 with a captureJobId.
- capture_job — args: { jobId }. Poll an async capture job. Read-only.
- query — args: { params? }. `params` is a key/value map of standard EPCIS query parameters (EQ_bizStep, GE_eventTime, MATCH_epc, …). Read-only.
tracepass_templates
Discover the regulatory field schema for each DPP category — what a COMPLIANT passport must contain, per the governing EU regulation. Read-only reference data. Use this to advise on requirements before creating products/passports, and to gap-check a draft against the rules.
Actions (pass via `action`, with `args`):
- list — args: {}. Lists all 13 categories with their field count, required-field count, and governing regulation (name + number + effective/mandatory dates).
- get — args: { category }. Full field schema for one category: every field's key, label, dataType, whether it is REQUIRED, its access level (public/restricted/authority), enum options, validation bounds, and — where known — the regulation article/annex that mandates it. `category` is one of: battery, textile, electronics, construction, steel, detergents, paints-coatings, packaging, furniture, tyres, jewelry, toys, fmcg.
BATTERY — required-ness is per-category, so `required` alone is the wrong answer. Resolve it in this order:
1. SCOPE FIRST. Only EV, LMT and industrial_gt_2kwh batteries owe a passport at all (Art. 77(1), Reg (EU) 2023/1542). For portable, SLI or industrial_lte_2kwh, NO field is required — do not list mandatory fields for them; say the battery is out of scope.
2. Then `requiredBy[batteryCategory]` where the field carries that map (required | conditional | notApplicable).
3. Then fall back to `required`.
The map is keyed ONLY by the three in-scope categories, so skipping step 1 falls through to `required` and invents an obligation the Regulation does not impose. Note also that EV and LMT report state-of-health through MUTUALLY EXCLUSIVE field sets — an EV battery must leave the remaining-capacity cluster empty and an LMT battery must leave stateOfCertifiedEnergy empty, so no single battery ever fills every field.