Demos · recorded on a live InfiPlex instance
These are recordings of Claude Desktop connected to a live InfiPlex instance through the InfiPlex MCP server. Nothing is staged inside a call: every answer comes from a tool the server exposes, on real orders and inventory, and every write stops at the server's preview until a person answers. Typing and tool waits are sped up, answers play at real speed. Each demo has chapters and a full transcript below it.
Demo 1
Chapters
| Time | What was asked | Tool the agent called | What came back |
|---|---|---|---|
| 0:03 | How many orders came in today, and how many are still unshipped? | order_search | 1 order today, still unshipped. |
| 0:16 | For the order today, what was the ship-to address and which warehouse(s) did it route to? | order_search | Order 103480 to Columbus, OH; split: HB-2201 from Reno, MK-88 from Columbus. |
| 0:30 | Why did it get routed to Reno? | order_warehouse_routing_explanation_get | Columbus passed zip rules but had 0 of HB-2201; Reno had 42, so the unit came from Reno. MK-88 stayed in Columbus. |
| 0:40 | Do I have any SKUs at the reorder point? | inventory_restock_list | Three: GL-410, GL-411, MK-88, with on hand and reorder point. |
| 0:53 | Add a note to order 103480 that the customer called about delivery. | order_note_create | Note added. |
| 1:05 | Set HB-2201 to $24.99. Then: actually, leave it. | price_get, price_set (preview) | Server previews the change from $27.50; declined in chat; no change made. |
| 1:20 | Show me Reno's routing settings. | warehouse_get | Reno's zip rules and why 43219 made it eligible for today's order. |
Transcript
You
How many orders came in today and how many are still unshipped?
Tool
order_search
Claude
1 order came in today on Mark8, and it is still unshipped.
You
For the order today, what was the ship to address and which warehouse(s) did it get routed to?
Tool
order_search
Claude
Order 103480 (Manual, 9:51 AM). Ship to: Jordan Rivera, 4400 Easton Way, Columbus, OH 43219, US. Routing: split across two warehouses.
You
Why did it get routed to Reno?
Tool
order_warehouse_routing_explanation_get
Claude
Columbus was checked first (passed zip rules, set as default), but it had 0 units of HB-2201 at routing time. Reno was checked next, also passed zip rules, and had 42 on hand, so the 1 unit was pulled from there. MK-88 stayed in Columbus because it had 4 on hand, enough to cover the 2 ordered.
You
Ok. Do I have any SKUs at the reorder point?
Tool
inventory_restock_list
Claude
Three SKUs at or below reorder point:
MK-88 dropped after today's order took 2 from Columbus.
You
Add a note to order 103480 that the customer called about delivery.
Tool
order_note_create
Claude
Note added to order 103480: "Customer called about delivery."
You
Set HB-2201 to $24.99
Tool
price_get, then price_set (first call: server returns the preview and a confirmation token; nothing is written)
Claude
HB-2201 is currently $27.50. Setting it to $24.99 will push to connected channels. Confirm?
You
Actually leave it at that
Claude
Left at $27.50, no change made.
You
Show me Reno's routing settings
Tool
warehouse_get
Claude
Reno (warehouse 14), Reno, NV 89502. Zip rules on, with the rule set that made it eligible; since 43219 matches the rule, Reno was eligible for today's order.
The routing answer at 0:30 is the one to notice. It is not the agent reasoning about what probably happened; it is the event log InfiPlex wrote when the order was allocated, returned by one tool. The price change at 1:05 is the other: the server issued the preview, the agent showed it, and a two-word reply ended it with nothing written. How every write is protected.
Do it yourself
Tools > Admin API > Create New API Key. Read scopes only for the first run. MCP Enabled: Yes. Set-up guide.
Claude: add a custom connector with your instance URL and the api-token header. Codex, Cursor, and others: the same two values in their config.
Orders today, one order's routing, why it routed there, the restock list, and a price change you decline. All prompts by role.
Add Write Orders and Write Inventory for tracking and receiving, or run the fully autonomous fulfillment agent. Headless order management explains the dial.
Frequently asked
Real. It is a screen recording of Claude Desktop connected to a live InfiPlex instance through the MCP server. The order, SKUs, and warehouses are sample records on that instance; every answer is what the tools returned. Typing and tool waits are sped up in the edit; nothing inside a tool call is cut.
Because the server makes it. Tools that change stock, prices, shipments, products, warehouses, or settings return a preview and a confirmation token on the first call and only execute on a second call carrying that token. The agent showed the preview and the person declined, so nothing was written. A fully autonomous agent completes that second call itself on a key you configure for it.
order_search, order_warehouse_routing_explanation_get, inventory_restock_list, order_note_create, price_get, price_set, and warehouse_get. All of them, with inputs and gates, are on the tools reference.
Yes, through Codex (the CLI and IDE extension), which supports remote MCP servers with a header. Cursor, Windsurf, and any MCP client work the same way. The ChatGPT web app itself requires OAuth for remote servers and is not supported at this time.
Nothing beyond API access, which is part of InfiPlex's Growth and Enterprise packages. No AI add-on and no per-call fee. See pricing.
Resources
Bring the question your team asks most. We will connect an agent to a live instance and answer it on the call, then hand you the key to do it yourself.
Open a key at Tools > Admin API, set MCP Enabled to Yes, and run the seven questions above. Questions: Contact us, email info@infiplex.com, or call 888‑770‑0857.
Recorded September 24, 2026 on a live InfiPlex instance with sample records. Claude is a trademark of Anthropic, PBC. ChatGPT and Codex are trademarks of OpenAI. Model Context Protocol is an open standard.
InfiPlex provides eCommerce companies, warehouses, and 3PLs with a robust platform to manage their sales channels.
©2026. All Rights Reserved. Privacy Policy | Terms & License