Hosted MCP servers for hardware engineering tools

Talk to your factory.
PLM, ERP & MES — one AI endpoint.

bomrail connects ION, Duro, Xero and the rest of your hardware stack to Claude and your AI agents. Ask about revisions, BOMs, ECOs and purchase orders — get answers across every system, with a full audit trail.

See how it works
Read-only by default · SOC 2 roadmap · Self-hosted option for ITAR
Claude · connected to bomrail MCP
Which open purchase orders are affected by ECO-142?
▸ bomrail.get_eco(eco_id: "ECO-142") — Duro PLM
▸ bomrail.find_pos_by_part(part: "PN-1042", rev: "C") — ION Factory OS
▸ bomrail.get_bill_status(po: ["PO-0871", "PO-0902"]) — Xero
ECO-142 bumps PN-1042 from rev C → D (new tolerance on the mounting flange). Two open POs still reference rev C:
PO Supplier Qty Status Xero bill
PO-0871 Apex Machining 40 Ordered Unpaid — $12,400
PO-0902 Vector Fab 15 Draft Not issued
PO-0871 Ordered
Apex Machining · Qty 40
Xero bill: Unpaid — $12,400
PO-0902 Draft
Vector Fab · Qty 15
Xero bill: Not issued

PO-0902 is still a draft — safe to update to rev D before release. PO-0871 is already ordered; want me to draft a change notice to Apex Machining?

Works with the tools hardware teams actually run

Live in an afternoon, not a quarter

No middleware project. No IT ticket. Connect your tools, drop one URL into Claude, and your whole team can query the digital thread.

1

Connect your tools

Sign into ION, Duro and Xero via OAuth. Your credentials stay encrypted; we never store raw engineering data.

2

Get your MCP endpoint

One URL for your whole stack: mcp.bomrail.com/acme. Add it to Claude, Claude Code, or any MCP-compatible agent.

3

Ask across systems

"Which suppliers are late on parts blocking WO-88?" — answers joined across PLM, ERP and MES, with sources cited.

Built for teams where mistakes cost real money

AI access to engineering data has to be safer than a shared spreadsheet — not the other way around.

Read-only by default

Agents can query anything, change nothing. Write actions — updating a PO, releasing an ECO — require explicit human approval per action.

Full audit trail

Every tool call is logged: who asked, what was accessed, what was returned. Exportable for your quality system and AS9100 audits.

ITAR-ready deployment

Export-controlled data can't live on someone else's multitenant cloud. Deploy bomrail in your own VPC or on-prem — same product, your perimeter.

Revision-aware answers

Built by people who’ve lived through ECO chaos. bomrail understands revisions, effectivity, and BOM structures — not just generic "records".

Full details on our security page — read-only defaults, audit exports, and the self-hosted ITAR deployment.

Popular integrations

Deep dives on what bomrail connects, pair by pair — see the full list on the integrations page.

New here? Start with what an MCP server is, explained for hardware teams.

Frequently asked questions

What is bomrail?

bomrail is a hosted MCP (Model Context Protocol) server service for hardware engineering systems. It connects PLM, ERP, MES and accounting tools — ION Factory OS, Duro PLM, Xero and others — to Claude and any MCP-compatible AI agent, so your team can ask questions about BOMs, revisions, ECOs, work orders, purchase orders and bills across every system in one conversation. Connections are read-only by default and every tool call is logged to an audit trail.

What is an MCP server?

MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude call external tools and read external data. An MCP server exposes a system — for example your PLM or ERP — as a set of typed tools the AI can call. bomrail hosts these servers for you: you sign in to your tools via OAuth once, and your whole team gets one MCP endpoint, with no integration code to write or infrastructure to run.

Which tools does bomrail support?

ION Factory OS, Duro PLM and Xero are live for design partners. NetSuite, Odoo, Arena PLM, Epsilon3 and QuickBooks connectors ship with the design-partner cohort — joining the waitlist with one of those in your stack moves it up the queue.

Can the AI change data in my PLM or ERP?

Not unless you explicitly allow it. bomrail connections are read-only by default: agents can query records but not create, update or delete them. Write actions are opt-in and gated behind per-action approvals, and every call — read or write — is logged with who asked, which tool ran, and what came back.

Does bomrail sync or store my engineering data?

No. bomrail is not a sync engine or a data warehouse — it reads your systems live at question time and joins the results in the answer. Each tool remains the source of truth for its own records. The only thing bomrail retains is the audit log of tool calls.

How is bomrail different from Zapier or a custom API integration?

Integration platforms move data between systems on triggers you configure in advance. bomrail instead lets an AI agent query your systems live and join the results on demand, so you are not limited to workflows someone predicted. Compared to building against each API directly, bomrail handles credential distribution, keeps tools current as vendor APIs evolve, and produces the audit trail your quality system expects.