Hosted MCP server for Duro PLM
Duro PLM holds the design intent of your product: part numbers, revisions, bills of materials, and the engineering change orders that move them. It is the system agents must consult before answering almost any "which version?" question — and the system most integrations get wrong, because revisions and effectivity do not map cleanly onto generic record models.
The bomrail hosted MCP server for Duro exposes revision-aware tools: fetch an ECO with its affected items, walk a BOM at a specific revision, diff two revisions of an assembly, and resolve where-used for any component. Answers come back structured, so an agent can reason about them instead of scraping UI text. Access is read-only by default, OAuth-scoped to your Duro workspace, and every call lands in the audit log.
Paired with your ERP or accounting connection, Duro data becomes actionable: the moment an ECO releases, an agent can tell you which open purchase orders, work orders, or supplier quotes still reference the superseded revision — the exact failure mode that quietly costs hardware teams scrap and rework.
What the Duro MCP server exposes
Typed, read-only tools over parts & revisions, BOMs, engineering change orders, documents, where-used references — callable by Claude, Claude Code, or any MCP-compatible agent:
bomrail.get_eco (eco_id) Fetch an ECO: status, affected items, revision bumps, and approvals.
bomrail.get_bom (assembly, rev?) Walk a bill of materials at a given revision, with quantities and reference designators.
bomrail.diff_revisions (part, rev_a, rev_b) Structured diff of two revisions: changed fields, BOM line changes, document changes.
bomrail.where_used (part) Every assembly that consumes a component, with revision effectivity.
Questions teams ask
- What changed between rev C and rev D of PN-1042?
- Which assemblies use the connector we are end-of-lifing?
- List ECOs released this month and their affected items.
Why not just use the Duro API directly?
You can — and for a single scripted workflow you should. bomrail earns its keep where direct API access gets expensive: distributing and rotating credentials across a team, keeping tools current as the Duro API evolves, and producing the audit trail your quality system expects when an AI is doing the reading. One OAuth sign-in, one MCP URL for the whole team, every call logged. Read more on the security page, or see what an MCP server is if the concept is new.