Medusa + Memtro

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.

In Memtro

What you can do with Medusa in Memtro

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.

What it does

  1. 01Orders newest first by status, customer, created date or a search term, with payment and fulfilment status and total
  2. 02One order in full: line items with title, variant, SKU, quantity, unit price and total, never addresses
  3. 03Customers by name, email or company, and products by title, handle or status, never phone numbers
  4. 04Inventory items with stocked, reserved and available quantities
  5. 05When asked and granted, creates or changes customers, creates a draft order or places it, fulfils, ships, completes, archives or cancels orders, with customer notification off unless asked
  6. 06When asked and granted, captures or refunds a payment, which moves money, creates, publishes or permanently deletes products, and sets stocked quantities

Acts when asked

When you ask it to

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.

  1. 01Create a customer record
  2. 02Create a draft order (not sent, charged or placed until someone converts it)
  3. 03Convert a draft order into a placed order (permanent)
  4. 04Fulfil items of an order (customer notification off unless asked)
  5. 05Mark a fulfilment shipped with tracking (customer notification off unless asked)
  6. 06Cancel a fulfilment that has not shipped
  7. 07Cancel an order (permanent)
  8. 08Mark an order completed
  9. 09Archive an order
  10. 10Change an order's email or shipping or billing address
  11. 11Capture an authorised payment (moves money)
  12. 12Refund a captured payment in full or part (moves money)
  13. 13Change a customer's name, email or company
  14. 14Create a product (draft unless a status is given)
  15. 15Change a product's title, description, handle or status
  16. 16Delete a product (permanent)
  17. 17Set the stocked or incoming quantity of an item at a location
In practice

Ask it like you would a colleague

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.

Medusa + Memtro
  • 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

01

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.

02

A partial refund

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.

Teams

Where it fits

The teams that lean on Medusa most, a question each of them asks, and what they connect beside it.

Better together

Works with

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.

Setup

How to connect

Connect withBackend host and secret API key
  1. 1

    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

  2. 2

    Copy the sk_ key, shown once

  3. 3

    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

  4. 4

    Ask what a customer ordered in the last month

Also works from

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.

FAQ

Questions

Can Memtro change anything in Medusa?+

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.

Who can use a Medusa connection?+

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.

Does Memtro store my Medusa data?+

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.

How do I connect Medusa?+

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.

Connect Medusa in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

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