Loop Returns MCP server
Loop Returns in any MCP client, through Memtro: Loop Returns does not publish this server. Memtro's Loop Returns connector reads Loop Returns 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
Loop Returns for Shopify: returns by state and date with their items, reasons, outcomes and label status, one return by id or order, its notes, the advanced shipping notice of returns in transit, and per-item return eligibility of an order; when you ask, can note, flag, process (issuing refunds and exchanges), close, cancel or remove items from a return, and create a return link for an order.
Reads
loopreturns_list_returnsLoop returns created (or updated) in a window, default the last 7 days, at most 120: state, outcome, order, item count…loopreturns_get_returnOne Loop return in detail, by its return id or by the order name (e.g. #1001) or the commerce provider's order id: state, outcome…loopreturns_return_notesThe internal notes on a Loop return, with when each was written.loopreturns_shipping_noticeLoop's advanced shipping notice: returned items in packages by date range (default the last week, at most 120 days), with the return, order…loopreturns_order_eligibilityWhich items of an order can be returned in Loop right now, and why not for the others (final sale, window closed, not delivered…)…
Acts, when you ask
These change something in Loop Returns. 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.
loopreturns_add_noteAdds an internal note (at most 255 characters) to a Loop return's timeline.loopreturns_flag_returnFlags a Loop return for review, which stops its automated processing until somebody reviews it in Loop Admin.loopreturns_process_returnProcesses a Loop return: archives it and fulfils its outcomes, issuing the refund, store credit or gift card and placing any exchange order…loopreturns_close_returnCloses a Loop return without fulfilling it: no refund, exchange or gift card is issued, the items cannot be used in a new return…loopreturns_cancel_returnCancels a customer's Loop return, freeing its items so the customer can start a new return.loopreturns_remove_itemsRemoves line items from an open Loop return whose outcome is all refund or all store credit, reducing what is refunded or credited.loopreturns_create_return_linkCreates a deep link that opens Loop's return portal straight at an order, so the customer need not look it up.
Connect it
First connect Loop Returns on Dashboard → Connections, then add Memtro to your client once. The Loop Returns 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 Loop Returns 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 returns are waiting to be processed?
- › Show the return for order #1001 with its reasons.
- › Which returned items are in transit this week?
- › Can the customer on order #1042 still return the jacket?
- › Flag the return on order #1001 for review.
Questions
- Is this an official Loop Returns MCP server?
- No. It is Memtro's MCP server with Memtro's Loop Returns connector behind it: the connector reads Loop Returns through its API with the credentials you connect on Dashboard → Connections, and Loop Returns 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 Loop Returns?
- Only when you ask, and only what it has been granted: add an internal note to a return; flag a return for review; process a return, issuing its refund, exchange or credit; close a return without fulfilling it; cancel a return; remove items from an open return; create a return link for an order. 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.