Skip to main content
This guide walks you through connecting an MCP-compatible client — Claude Desktop, Cursor, VS Code Copilot, or any other client that speaks the Model Context Protocol — to your Loop Returns account.

​
Prerequisites

  • A Loop Returns account in good standing
  • A user account with the permissions you want the assistant to be able to use (the MCP server enforces the same role-based permissions as the Loop Admin)
  • An MCP-compatible client installed locally

​
The Loop MCP endpoint

https://api.loopreturns.com/mcp
All MCP traffic goes to that single URL. Authentication is negotiated automatically by the client through the OAuth Protected Resource Metadata discovery endpoint at /.well-known/oauth-protected-resource.

​
Connect a client

Claude Desktop’s local developer config connects to local command-based MCP servers. Use mcp-remote to bridge Claude Desktop to Loop’s hosted MCP endpoint.
  1. Open Settings → Developer → Edit Config in Claude Desktop.
  2. Add Loop to your mcpServers block:
{
  "mcpServers": {
    "loop-returns": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.loopreturns.com/mcp"
      ]
    }
  }
}
  1. Restart Claude Desktop. The Loop server appears in the Connectors list.
  2. Click Connect next to loop-returns. A browser window opens to Loop’s OAuth flow — sign in with your Loop credentials and approve access.

​
Multi-shop accounts

If your email is associated with more than one Loop shop, the OAuth flow shows a shop selector after you sign in. Pick the shop you want to grant the assistant access to. You can disconnect and reconnect to switch shops. If your MCP client supports multiple server entries, create one Loop server per shop and name each entry after the shop, for example loop-returns-store-a and loop-returns-store-b. Each entry runs the same endpoint but keeps its own OAuth connection, making it easier to choose the right shop before asking the assistant to act.

​
Verify the connection

Once connected, ask the assistant:
“What Loop shop am I connected to?”
The assistant should call the get_shop_info tool and respond with your shop’s name and ID. For users who belong to more than one Loop shop, this confirms the assistant is scoped to the shop selected during OAuth before you ask it to inspect or change returns. If you see an error about authentication or permissions, see the Authentication guide.

​
Try a few prompts

Show me the most recent 5 returns flagged for review.

Get the timeline for return #1234 and summarize what happened.

List the active workflows in my shop.

​
Rate limits

LimitScope
600 tool calls per hourPer authenticated user
100 OAuth authorizations per hourPer IP
100 token requests per hourPer IP
If you hit a rate limit, the assistant will surface the error and back off automatically. Heavy programmatic workloads should use the REST API instead.

​
Disconnect

To revoke access, disconnect the Loop server in your MCP client and revoke the session in Loop Admin → Settings → Developers (coming soon — for now, contact support to revoke a session immediately).

​
Next steps

Authentication

Understand the OAuth flow and how shops are scoped to tokens.

Overview

See the full list of tools and resources the MCP server exposes.