Late production check
Tom Reilly, production manager at Acme Ltd, asked which manufacturing orders were behind. Memtro listed each late order with its product, due date, delay in days and parts booking status.
Which manufacturing orders are running late, and what are they waiting for?
MRPeasy runs your production, and Memtro reads it so you can ask about orders and stock in plain words. It reads customer orders with status, invoicing, payment, cost and profit, and manufacturing orders with due dates, delays and costs. It reads purchase orders, stock quantities, inventory value on any date, shipments with tracking, invoices and customers. When asked and granted, it can manage stock items and record or cancel a vendor's invoice. With the Pro API it can also schedule, book parts for, finish or close manufacturing orders. The API needs the Unlimited plan.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right MRPeasy tool, reads what it needs, and answers with the source cited.
These tools change something in MRPeasy. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once MRPeasy is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which manufacturing orders are past their due date?
What was our inventory value at the end of last month?
Which purchase orders are expected to arrive this week?
Which customer invoices are unpaid and past their due date?
Book all parts for manufacturing order MO-0412.
Tom Reilly, production manager at Acme Ltd, asked which manufacturing orders were behind. Memtro listed each late order with its product, due date, delay in days and parts booking status.
Sarah Chen, purchasing lead at Northwind, asked Memtro to record a vendor's invoice against a purchase order. Memtro recorded it with the vendor's invoice number, so MRPeasy also posted it to Xero for the finance team.
The teams that lean on MRPeasy most, a question each of them asks, and what they connect beside it.
A record in MRPeasy is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In MRPeasy, go to Settings, then Integration, then API access, set an API key and secret and save. The API needs the Unlimited plan.
In Memtro, open Connections → MRPeasy and paste the API key and the API secret.
The key and secret reach the whole account. An administrator grants the stock, invoice and manufacturing actions by name only to the teams that need them.
Ask which manufacturing orders are running late.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The MRPeasy tools are the same everywhere.
Only when you ask, and only what it has been granted: create a stock item; update a stock item; delete a stock item; record a vendor's incoming invoice against a purchase order; cancel an incoming invoice; schedule a manufacturing order (Pro API); book all parts for a manufacturing order (Pro API); release a manufacturing order's booked parts (Pro API); finish a manufacturing order as planned, consuming materials (Pro API); close a finished manufacturing order (Pro API). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key and API secret. In MRPeasy, go to Settings, then Integration, then API access, set an API key and secret and save. The API needs the Unlimited plan.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time