# Inventory MCP: an AI that knows every part on the shelf

> Ondes PRO’s inventory MCP server: your AI checks stock levels, logs deliveries, reads bills of materials and drafts production orders you approve first.

Updated on 2026-10-21 · The Ondes PRO team · https://ondes.pro/en/integrations/mcp/modules/inventory

Ondes PRO’s **MCP server** gives your AI assistant access to your workspace’s inventory: components, assembled products, bills of materials, stock movements and production orders. It answers “how many can we build?” from real quantities, logs a delivery and drafts a production order for you to approve — without ever rewriting the movement history.

## An order for 12 lamps: can we build them?

_Example conversation · demo data (Atelier Lumen)_

> **You** : How many Tripod lamps can we assemble from what’s in stock? We need 12.
>
> 🔧 `ondes_chercher` “bill of materials” → resource `inventory/assemblages`, action `nomenclature/`.
>
> 🔧 `ondes_appeler` `GET inventory/assemblages/18/nomenclature/` — 4 finished Tripod lamps, 7 buildable, linen shades are the bottleneck.
>
> **Assistant** : You have **4 Tripod lamps** ready and parts to assemble **7** more, so 11 in total. The twelfth is blocked by linen shades: 7 left, one per lamp. I can draft a production order for 7 lamps and remind you to reorder shades.
>
> **You** : Draft the order, but show me what it will use up first.
>
> 🔧 `ondes_appeler` `POST inventory/assemblages/18/assembler/` with `apercu: true` — nothing written: 7 brass bases, 7 shades, 7 fabric cables.
>
> 🔧 `ondes_appeler` `POST inventory/ordres-production` then `inventory/lignes-production` — order #57 created as a draft (real write stated).
>
> **Assistant** : Order #57 is a draft for 7 lamps. Nothing has been consumed yet: parts are only used when you run the order from the workshop.

## What your AI can read and do in inventory

Ondes PRO’s inventory separates **components** (what you buy), **assembled products** (what you make, each with its bill of materials) and the **movements** that record every unit in and out. The assistant reads all three live, along with the low-stock thresholds you have set.

It can also do the maths: a product’s `nomenclature/` action says how many units the parts on hand can build, and `estimer/` evaluates a bill of materials that does not exist yet — handy for costing a new model before you create it. On the write side, it logs a delivery, adjusts a bill of materials, and drafts and schedules a production order.

## Inventory resources available over MCP

| Resource | What the AI reads | What the AI can do |
| --- | --- | --- |
| `inventory/composants` | Quantities, references, low-stock threshold, category | Create a component, edit its record |
| `inventory/assemblages` | Finished products, stock, bill of materials, missing parts | Edit the bill of materials, `assembler/` (with preview) |
| `inventory/mouvements` | Log of stock in and out | Append a movement (delivery, issue, correction) |
| `inventory/ordres-production` | Open orders and their status | Create, `planifier/`, `executer/`, `annuler/` |
| `inventory/lignes-production` | Products to assemble in an order | Add or edit a line |
| `inventory/liaisons-boutique` | Link between a product on sale and stock | Link a product (also requires Store permissions) |
| `inventory/categories` | Component categories | Create a category |

## Reliable stock, even when an AI writes to it

Stock is accounting data as much as operational data. The safeguards live in the API itself.

- **Movements are appended, never rewritten**: `inventory/mouvements` only allows reading and adding. A mistake is fixed with a reverse movement, and the history stays intact.
- **Preview before consuming**: `assembler/` with `apercu: true` shows which parts would be used without writing anything. For a create or an update, `simuler: true` checks the request body, again without saving anything.
- **Two-step orders**: a production order starts as a draft, gets scheduled, then runs. Components are only consumed when it runs.
- **Real writes are flagged**: these resources have no test twin, so every write is reported as real in the response — the assistant sees it and can tell you.
- **All or nothing**: assisted creation of a product with its stock refuses as a whole (listing missing parts) rather than leaving a half-written state.

## Typical requests and what happens

| You ask | What the assistant does |
| --- | --- |
| “Which components are below their threshold?” | Reads `inventory/composants` and compares each quantity with its threshold. |
| “We just received 50 black fabric cables.” | Appends an incoming movement to `inventory/mouvements`. |
| “What would an XL Pétrole pendant cost to make?” | Calls `inventory/assemblages/estimer/` with the proposed bill of materials. |
| “Start production of 20 Brass pendants.” | Creates the draft order, shows the preview, schedules it once you approve. |
| “I counted 3 extra bases.” | Logs a correction movement without touching past movements. |

## From stock to quote in the same conversation

An MCP server limited to inventory answers the quantity question and stops there. With Ondes PRO, the answer can immediately become a quote in [invoicing](https://ondes.pro/en/integrations/mcp/modules/invoicing), a workshop card in [Kanban](https://ondes.pro/en/integrations/mcp/modules/kanban) with the expected finish date, or a product update in [the online store](https://ondes.pro/en/integrations/mcp/modules/online-store).

Online sales linked to stock deduct the sold units automatically. The assistant can therefore match what leaves through the store against what the workshop has to build, and flag the next shortage before an order exposes it.

> **Several companies, several stocks** — If your group runs several companies, each subsidiary keeps its own stock. The assistant targets the company you choose and never sees a sister company’s stock beyond your permissions. From the parent company view, it can consolidate everything.

## Keep exploring

- [Manufacturers](https://ondes.pro/en/integrations/mcp/industries/manufacturing) — Components, bills of materials, production orders and low stock: the AI spots bottlenecks before you do.
- [Small businesses and trades](https://ondes.pro/en/integrations/mcp/industries/small-businesses) — Quotes, invoices, reminders and scheduling prepared by AI and approved by you, even between jobs.
- [Modules available over MCP](https://ondes.pro/en/integrations/mcp/modules) — Eleven business modules behind one MCP server: what the assistant can read and do in each.

## Frequently asked questions

### Can I connect an AI to my inventory software?

Yes, if the software exposes an MCP server. Ondes PRO builds one into every workspace: Claude or any other MCP-compatible client can read components, assembled products and movements, and draft production orders.

### Can the AI delete a stock movement?

No. Stock movements cannot be deleted or edited: `inventory/mouvements` only allows reading and adding. A mistake is corrected with a reverse movement.

### Will the assistant use up parts without warning?

Parts are only consumed when a production order or an assembly runs. Before that, the assembly preview (`apercu: true`) shows which parts would be used, without writing anything.

### Can it work out how many units we can build?

Yes. An assembled product’s `nomenclature/` action says how many units the parts in stock can build, and which part is the bottleneck.

### Do store sales update stock?

Yes, for products linked to stock through `inventory/liaisons-boutique`: each sale deducts the number of units set on the link.