Hosted MCP server for ION Factory OS
ION Factory OS is the manufacturing backbone for a new generation of aerospace and hardware companies: work orders, purchase orders, inventory, receiving, and as-built traceability live there. That makes it the single most useful system to put in front of an AI agent — almost every operational question ("is this part in stock?", "what is blocking this build?", "which POs are late?") is ultimately an ION query.
The bomrail hosted MCP server for ION Factory OS wraps the ION API in a set of typed, read-only tools that Claude and other MCP-compatible agents can call directly. You do not write integration code, host anything, or hand an agent raw API keys: you sign into ION via OAuth once, and bomrail exposes a scoped endpoint your whole team can use. Every call is logged with the user, the tool, the arguments, and a hash of the response, so your quality team can reconstruct exactly what the AI saw.
Because bomrail also connects your finance and PLM systems, ION data stops being an island. An agent can chase a question from an ION work order to the Duro ECO that caused a shortage to the Xero bill that has not been paid — in one conversation, with each hop cited.
What the ION MCP server exposes
Typed, read-only tools over work orders, purchase orders, inventory & lots, parts & part revisions, receiving records, suppliers — callable by Claude, Claude Code, or any MCP-compatible agent:
bomrail.get_work_order (wo_id) Fetch a work order with status, operations, and blocking issues.
bomrail.find_pos_by_part (part, rev?) List open purchase orders that reference a part number, optionally filtered by revision.
bomrail.get_inventory (part, location?) On-hand quantity, lots, and reservations for a part.
bomrail.list_late_pos (days_overdue?) Purchase orders past their promised date, with supplier contacts.
bomrail.get_part (part) Part master record: revision, sourcing, and open demand.
Questions teams ask
- Which suppliers are late on parts blocking WO-88?
- Do we have enough PN-2210 rev B on hand to start the next build?
- List every open PO over $10k and when it was promised.
Why not just use the ION 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 ION 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.