AfterShip MCP server
AfterShip in any MCP client, through Memtro: AfterShip does not publish this server. Memtro's AfterShip connector reads AfterShip 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
AfterShip shipment tracking: trackings by status, courier, order or date changed, one tracking with its checkpoint history (city and country only), and the couriers enabled on the account. Can create, update, retrack, mark completed and delete trackings, without contacting buyers.
Reads
aftership_trackingsAfterShip trackings: tracking number, courier, order, status (Pending, InTransit, OutForDelivery, Delivered, Exception…), latest checkpoint…aftership_trackingOne AfterShip tracking by its id (from aftership_trackings) with its checkpoint history, newest last: time, status, the courier's message…aftership_couriersCouriers enabled on the AfterShip account: slug (used to filter trackings), name, website and the extra fields a tracking with that courier needs.
Acts, when you ask
These change something in AfterShip. 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.
aftership_create_trackingStarts tracking a shipment in AfterShip by its tracking number, optionally with the courier slug (else AfterShip detects it), a title…aftership_update_trackingChanges an AfterShip tracking's title, note (replaces the old note), store order id or number, courier slug or shipping method.aftership_retrack_trackingRetracks an AfterShip tracking that has stopped updating (expired or marked completed), so AfterShip polls the courier again.aftership_mark_tracking_completedCloses an AfterShip tracking as DELIVERED, LOST or RETURNED_TO_SENDER, which sets its status and stops AfterShip updating it until it is retracked.aftership_delete_trackingDeletes an AfterShip tracking and its checkpoint history, permanently.
Connect it
First connect AfterShip on Dashboard → Connections, then add Memtro to your client once. The AfterShip 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 AfterShip 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
- › Which AfterShip shipments are stuck in exception?
- › Where is order 1042?
- › Which deliveries this week were not on time?
- › Which couriers do we have enabled?
- › Start tracking 1Z999AA10123456784 for order 1042.
Questions
- Is this an official AfterShip MCP server?
- No. It is Memtro's MCP server with Memtro's AfterShip connector behind it: the connector reads AfterShip through its API with the credentials you connect on Dashboard → Connections, and AfterShip 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 AfterShip?
- Only when you ask, and only what it has been granted: start tracking a shipment by its tracking number; change a tracking's title, note, order id or number, courier or shipping method; retrack an expired tracking (allowed once per shipment); mark a tracking completed as delivered, lost or returned to sender; delete a tracking, permanently. 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.
