Getting Started

This guide walks you through connecting an MCP-compatible client — Claude, Cursor, VS Code Copilot, ChatGPT, Microsoft Copilot Studio, 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.

Supported clients

Loop validates the OAuth redirect URI against a fixed allowlist. These clients connect without extra setup:

Client	Redirect target
Claude (desktop and web)	`claude://`, `claude.ai`, `claude.com`
Cursor	`cursor://`
VS Code Copilot	`vscode://`, `vscode.dev`
ChatGPT	`chatgpt.com`, `chat.openai.com`
Microsoft Copilot Studio and Power Platform custom connectors	`global.consent.azure-apim.net`
Desktop and CLI clients on your machine	`http://localhost:<port>`

If your hosted client authenticates through your own domain, contact your Loop point of contact before you connect. Loop adds approved redirect domains to the allowlist. Loop does not trust arbitrary redirect URIs supplied at registration time.

Connect a client

Claude directory
Claude Desktop
Claude organization connector
Cursor
VS Code Copilot

Loop is listed in the Claude connector directory. Add it without editing a config file:

Open Settings → Connectors in Claude.
Browse the connector directory and select Loop Returns.
Click Connect. A browser window opens to Loop’s OAuth flow — sign in with your Loop credentials and approve access.

A Claude organization admin can enable Loop for the whole workspace. The admin adds Loop as an organization connector in Settings → Connectors. Each user still completes the Loop sign-in once, and Loop enforces that user’s existing Loop Admin permissions.

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.

Open Settings → Developer → Edit Config in Claude Desktop.
Add Loop to your mcpServers block:

{
  "mcpServers": {
    "loop-returns": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.loopreturns.com/mcp"
      ]
    }
  }
}

Restart Claude Desktop. The Loop server appears in the Connectors list.
Click Connect next to loop-returns. A browser window opens to Loop’s OAuth flow — sign in with your Loop credentials and approve access.

Claude Team and Enterprise admins can enable Loop for the organization from the Claude connector directory. Prefer that path when Loop is available in the directory.To add Loop as a custom organization connector instead:

In Claude, open Organization Settings → Connectors.
Create a custom connector for your organization.
Use the Loop MCP endpoint as the connector URL:

https://api.loopreturns.com/mcp

Publish or enable the connector for the organization.

Each user still authenticates with their own Loop credentials the first time they use the connector, and Loop enforces that user’s existing Loop Admin permissions.

Open Cursor Settings → MCP.
Add a new server with:

{
  "mcpServers": {
    "loop-returns": {
      "url": "https://api.loopreturns.com/mcp"
    }
  }
}

Cursor opens the OAuth flow in a browser. Sign in with your Loop credentials and approve access.

Open Settings → Copilot → MCP Servers.
Add the server:

{
  "loop-returns": {
    "url": "https://api.loopreturns.com/mcp"
  }
}

Reload the window. When you first invoke a Loop tool, Copilot prompts you to authenticate. 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

Limit	Scope
600 tool calls per hour	Per authenticated user
100 OAuth authorizations per hour	Per IP
100 token requests per hour	Per 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).

Introduction

Tool Reference

Prerequisites

The Loop MCP endpoint

Supported clients

Connect a client

Multi-shop accounts

Verify the connection

Try a few prompts

Rate limits

Disconnect

Next steps

Authentication

Overview

​Prerequisites

​The Loop MCP endpoint

​Supported clients

​Connect a client

​Multi-shop accounts

​Verify the connection

​Try a few prompts

​Rate limits

​Disconnect

​Next steps

Authentication

Overview

Prerequisites

The Loop MCP endpoint

Supported clients

Connect a client

Multi-shop accounts

Verify the connection

Try a few prompts

Rate limits

Disconnect

Next steps