Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.loopreturns.com/llms.txt

Use this file to discover all available pages before exploring further.

The Loop MCP Server is currently in preview. Functionality and tool surfaces may change before general availability. Reach out to your Loop point of contact for access.

​
What is the Loop MCP Server?

The Loop MCP Server is a Model Context Protocol server that lets AI assistants — Claude, Cursor, VS Code Copilot, ChatGPT, and any other MCP-compatible client — interact with the Loop Returns platform on a merchant’s behalf. Once a merchant connects their MCP client to Loop, the assistant can:
  • Look up returns, orders, and policies
  • Take actions on returns (approve, reject, cancel, close, flag, process, add notes)
  • Manage allowlist and blocklist entries
  • Read and write workflow rules
  • Report fraud and review fraud categories
  • Render interactive return cards inside the assistant via Generative UI
All requests are authenticated via OAuth 2.1 (with PKCE) against the merchant’s Loop account, and every tool call is gated by the same role-based permissions used in the Loop Admin.

​
Why MCP?

The MCP server is the right fit when you want an assistant to act on Loop data conversationally — for example, “Show me the last 10 returns flagged for fraud and reject any from this email address.” It complements the REST API and outgoing webhooks rather than replacing them:
SurfaceBest for
REST APIServer-to-server integrations and bespoke applications
WebhooksReacting to events as they happen
MCP ServerLetting an AI assistant operate Loop on a merchant’s behalf

​
Available tools

Tools are grouped by domain. Every tool enforces the merchant’s existing permissions — if the user can’t perform the action in the Loop Admin, the assistant can’t either. 22 tools are available today across six groups:
GroupToolsReference
Shop & PolicyGet shop info, read return policiesReference
Returns — ReadList returns, get return details, get return timelineReference
Returns — ActionsAdd note, flag, unflag, reject, cancel, close, processReference
FraudList fraud categories, report fraudReference
Allowlist & BlocklistList, add, and remove entries on either listReference
WorkflowsList workflows, get workflow detailReference

​
Generative UI

When an assistant takes an action on a return — for example, processing or rejecting it — Loop returns a UI spec alongside the text response. MCP clients that support MCP Apps render this spec into an interactive card with status badges and action buttons, so merchants can confirm what happened without leaving the chat. The interactive shell is served as an MCP resource (ui://loop/returns-app) and is built on Vue 3.

​
Endpoint

The production MCP endpoint is: 
https://api.loopreturns.com/mcp
OAuth discovery metadata is available at: 
https://api.loopreturns.com/.well-known/oauth-protected-resource
https://api.loopreturns.com/.well-known/openid-configuration

​
Next steps

Get Started

Connect Claude, Cursor, or VS Code Copilot to the Loop MCP Server in a few minutes.

Authentication

Learn how OAuth 2.1 with PKCE keeps merchant data scoped to the right shop.