Is this an official Sendcloud MCP server?

No. It is Memtro's MCP server with Memtro's Sendcloud connector behind it: the connector reads Sendcloud through its API with the credentials you connect on Dashboard → Connections, and Sendcloud publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

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 Sendcloud?

Only when you ask, and only what it has been granted: announce a shipment to a carrier and buy its label (spends money); buy a label for an imported shop order (spends money); cancel an announced shipment; create a customer return, with tracking emails only if asked; request cancellation of a return; update an order's status, notes, tags or shipping address; cancel a booked carrier pickup. 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.

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.

MCP server · Shipping and delivery

Sendcloud MCP server

Sendcloud in any MCP client, through Memtro: Sendcloud does not publish this server. Memtro's Sendcloud connector reads Sendcloud 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

Sendcloud shipping: shipments with carrier, parcel status and tracking, shop orders with status, totals and payment state, customer returns, and shipping options; on request it announces shipments and buys labels (spends money), cancels shipments, creates and cancels returns, updates an order's status, notes, tags or address, and cancels pickups.

Reads

sendcloud_list_shipping_optionsShipping options Sendcloud offers this account for a route: each option's code (needed to announce a shipment, buy a label or create a return), name…
sendcloud_list_shipmentsShipments in Sendcloud: order number, carrier, recipient name and town, and each parcel's status, tracking number and link.
sendcloud_list_ordersShop orders Sendcloud has imported from the connected stores: order number, status, order and update dates, item count, total, payment status…
sendcloud_list_returnsCustomer returns in Sendcloud created in a date range: status, reason, order number, tracking, label cost and return fee, delivery date.

Acts, when you ask

These change something in Sendcloud. 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.

sendcloud_create_shipmentAnnounce a shipment to the carrier and buy its label, charged to the account's carrier contract (spends money).
sendcloud_create_label_for_orderBuy a shipping label for one shop order Sendcloud has imported, announcing a shipment to the carrier (spends money on the account's carrier contract).
sendcloud_cancel_shipmentCancel an announced Sendcloud shipment, voiding its label, if the carrier supports cancellation.
sendcloud_create_returnCreate a customer return in Sendcloud: a return label from the customer's address back to yours, charged to the account's carrier contract…
sendcloud_cancel_returnRequest cancellation of a Sendcloud return.
sendcloud_update_orderUpdate one imported order in Sendcloud: its status, internal notes, tags (the list given replaces the current tags) or shipping address.
sendcloud_cancel_pickupCancel a booked carrier pickup, if the carrier and the pickup allow it.

Connect it

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

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=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-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

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 Sendcloud 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

› Where is the parcel for order 1234?
› What shipped yesterday, and with which carrier?
› Which returns came in this month, and why?
› Ship order 4821 with the standard DPD option
› Create a return for Priya Sharma's order and email her the tracking

Questions

Is this an official Sendcloud MCP server?: No. It is Memtro's MCP server with Memtro's Sendcloud connector behind it: the connector reads Sendcloud through its API with the credentials you connect on Dashboard → Connections, and Sendcloud 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 Sendcloud?: Only when you ask, and only what it has been granted: announce a shipment to a carrier and buy its label (spends money); buy a label for an imported shop order (spends money); cancel an announced shipment; create a customer return, with tracking emails only if asked; request cancellation of a return; update an order's status, notes, tags or shipping address; cancel a booked carrier pickup. 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.