Checking an order
Support asks what Northwind ordered last week. Memtro finds the order, lists its four line items with SKU, quantity and unit price, and says payment is captured but fulfilment has not started, without showing the delivery address.
Ask what a customer ordered recently in Medusa, and what is still in stock.
Connect Medusa with your backend host and a secret API key and Memtro reads orders with their status, payment and fulfilment status, totals and line items, plus customers, products and inventory quantities. Addresses, phone numbers and payment details are never returned. When you ask, and once an administrator has granted them by name, it can create customers, draft and place orders, fulfil and ship them, cancel or archive orders, change products and stock, and capture or refund payments, which moves money. Placing or cancelling an order, refunds and product deletes are permanent, and customers are notified only when asked.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Medusa tool, reads what it needs, and answers with the source cited.
These tools change something in Medusa. 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 Medusa 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.
What has Brightwave Ltd ordered from us this quarter?
Which orders are paid but not yet fulfilled?
How many of the blue hoodie are available in stock?
Create a draft order for priya@acme.example with two of the large mugs
Refund 20 pounds on Northwind's last order for the damaged mug
Support asks what Northwind ordered last week. Memtro finds the order, lists its four line items with SKU, quantity and unit price, and says payment is captured but fulfilment has not started, without showing the delivery address.
A Globex customer reports one damaged mug, and Dan Fletcher asks Memtro to refund it. With the action granted, Memtro refunds that amount on the captured payment through the store's payment provider, which moves the money back to the customer and cannot be undone.
The teams that lean on Medusa most, a question each of them asks, and what they connect beside it.
A record in Medusa 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 Medusa Admin open Settings → Developer → Secret API Keys → Create and name it Memtro. It carries full admin rights with no scopes, so make one for Memtro alone. A publishable pk_ key does not work, and Medusa v2 only
Copy the sk_ key, shown once
In Connections → Medusa in Memtro type the Backend host only (where /admin is served), with no https:// or path, a public DNS name with a publicly trusted certificate, and paste the Secret API key
Ask what a customer ordered in the last month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Medusa tools are the same everywhere.
Only when you ask, and only what it has been granted: create a customer record; create a draft order (not sent, charged or placed until someone converts it); convert a draft order into a placed order (permanent); fulfil items of an order (customer notification off unless asked); mark a fulfilment shipped with tracking (customer notification off unless asked); cancel a fulfilment that has not shipped; cancel an order (permanent); mark an order completed; archive an order; change an order's email or shipping or billing address; capture an authorised payment (moves money); refund a captured payment in full or part (moves money); change a customer's name, email or company; create a product (draft unless a status is given); change a product's title, description, handle or status; delete a product (permanent); set the stocked or incoming quantity of an item at a location. 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.
Backend host and secret API key. In Medusa Admin open Settings → Developer → Secret API Keys → Create and name it Memtro. It carries full admin rights with no scopes, so make one for Memtro alone. A publishable pk_ key does not work, and Medusa v2 only.
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