NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro
MCP server · Shipping and delivery

ShipEngine MCP server

ShipEngine in any MCP client, through Memtro: ShipEngine does not publish this server. Memtro's ShipEngine connector reads ShipEngine through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Rate, track and label parcels across every carrier a ShipEngine account has connected — Royal Mail, Parcelforce, DPD, Evri, InPost, Yodel, UPS, FedEx, DHL — with the shipper's own negotiated rates. Reads carriers, quotes, tracking, address checks and collection points; can also buy a label, void one and book or cancel a collection when you ask it to.

Reads

  • shipengine_carriersThe carriers this ShipEngine account has connected, with each one's id, the services it offers and the account balance where the carrier exposes one.
  • shipengine_ratesQuote a parcel across carriers and services: what each would charge and how long it would take.
  • shipengine_trackWhere a parcel is: the carrier's current status, the last scan and its events, by tracking number or by the id of a label bought here.
  • shipengine_validate_addressCheck an address against the carrier's own address data before anything is sent to it: whether it is deliverable, how the carrier would normalise it…
  • shipengine_service_pointsCollection points, lockers and shops near an address — InPost lockers, Evri ParcelShops, DPD pickup points…
  • shipengine_labelsLabels already bought on this account, with what each cost, its tracking number and whether it has been voided.

Acts, when you ask

These change something in ShipEngine. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • shipengine_buy_labelBuys a shipping label for a rate that shipengine_rates already quoted.
  • shipengine_void_labelVoids a label that was bought and asks the carrier to refund it.
  • shipengine_schedule_pickupBooks a carrier collection for labels already bought.
  • shipengine_cancel_pickupCancels a booked carrier collection.

Connect it

First connect ShipEngine on Dashboard → Connections, then add Memtro to your client once. The ShipEngine tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared ShipEngine connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › What is the cheapest way to send a 1.2kg parcel to Bristol today?
  • › Where is this customer's parcel, and when did the carrier last scan it?
  • › Which parcels have had no scan in 48 hours?
  • › Is this address deliverable before I buy the label?
  • › Which lockers are near BS1 4ST?

Questions

Is this an official ShipEngine MCP server?
No. It is Memtro's MCP server with Memtro's ShipEngine connector behind it: the connector reads ShipEngine through its API with the credentials you connect on Dashboard → Connections, and ShipEngine publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in ShipEngine?
Only when you ask, and only what it has been granted: buy a shipping label against a rate that was already quoted, which spends money on the carrier account; void a bought label and request a refund from the carrier; book a carrier collection; cancel a booked collection. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Shipping and delivery