Where is it
A customer asks where their parcel has got to. Support gives Memtro the tracking number and carrier, and it reads the current status, the last scan location and the ETA, so the reply goes out in a minute.
Shipments, labels and tracking from your Shippo account, answered without opening it.
Connect Shippo with an API token and Memtro reads the carrier accounts you have connected, your shipments with every rate quoted, labels with tracking number, status and label link, orders, and where any parcel is. There is no hourly sync. When asked, and once an administrator has granted each action by name, it saves addresses and parcels, creates customs declarations, shipments and orders, gets labels at quoted rates, requests label refunds, creates manifests and books pickups. A label on a live token charges postage to the account, and a refunded label or booked pickup cannot be undone here.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Shippo tool, reads what it needs, and answers with the source cited.
These tools change something in Shippo. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Shippo for you. Each event can start a job, with the event as its input. Shippo sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Shippo 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.
Where is Royal Mail parcel AB123456789GB right now?
Which labels bought this week are still showing PRE_TRANSIT?
What was the cheapest rate quoted on the shipment to Munich yesterday?
Which Shopify orders from the last three days have no label yet?
Get rates for a 2 kg parcel to the Northwind office in Leeds and take the cheapest next-day one
A customer asks where their parcel has got to. Support gives Memtro the tracking number and carrier, and it reads the current status, the last scan location and the ETA, so the reply goes out in a minute.
Leo Grant asks Memtro to send a replacement to Acme in Bristol. Memtro creates the shipment, lists the quoted rates, and once Leo confirms the carrier, service and price, gets the label on the live token. The postage is charged to the Shippo account and Memtro returns the tracking number and label link.
The teams that lean on Shippo most, a question each of them asks, and what they connect beside it.
A record in Shippo 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 Shippo open API Configuration → Developer Keys, choose Live keys or Test keys, and create a new key. It is shown once
Use a shippo_live_… key for the real shipments, labels and orders. A shippo_test_… key sees test objects only, spends nothing, and has a tighter rate limit on list reads
In Memtro open Connections → Shippo, paste the API token and connect. Memtro notes which carrier accounts it can see
Ask where a parcel is, or which labels bought this week are still in transit
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Shippo tools are the same everywhere.
Only when you ask, and only what it has been granted: save an address, optionally validated by Shippo; save a parcel's dimensions and weight; create a customs declaration with its items for an international shipment; create a shipment so carriers quote rates (buys nothing); create an order in Shippo; buy a shipping label from a quoted rate, which spends money on a live token; request a refund of an unused label, which cannot be undone; create a manifest (SCAN form) for named labels with one carrier; book a carrier pickup for named labels, which sends the carrier to the address. 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 token. In Shippo open API Configuration → Developer Keys, choose Live keys or Test keys, and create a new key. It is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Shippo for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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