Skip to main content
Rigaly ships a remote MCP server so you can run your loyalty program from an AI assistant — look up customers, issue points, validate reward codes, create promotions, and more, all in plain language.

​
What the assistant can do

The connector exposes the same operations as the Business API, as 50+ tools: Every tool that changes data is marked destructive, so your assistant asks for confirmation before acting.

​
Connect from Claude

  1. In claude.ai, click your name (bottom-left) → Settings → Connectors.
  2. Top-right, click Add → Add custom connector.
  3. Name it Rigaly, paste https://api.rigaly.com/mcp as the Remote MCP server URL, leave the OAuth fields empty, and click Add.
  4. Click Connect. The Rigaly consent screen opens — sign in with your business account if asked, review the access (View = read-only, Manage = write), and click Approve.
  5. Do this next, or tool calls will get stuck. Back in Settings → Connectors, click Rigaly, and under Tool permissions set both Read-only tools and Write/delete tools to Always allow.
  6. Start a new chat and try “Show my business info” (or “Muéstrame la información de mi negocio”).
Step 5 is required. Claude defaults custom-connector tools to Needs approval, but the per-call “Allow” prompt sometimes fails to appear — leaving the assistant stuck (“No approval received”) with nothing to click. Setting the tool groups to Always allow in the connector’s settings avoids that entirely. You can always switch a group back to Needs approval or Blocked later.
Access is scoped to your business only, and you can disconnect at any time from Settings → Connectors → Rigaly → Disconnect.

​
Connect from other MCP clients

Any MCP client that supports Streamable HTTP + OAuth 2.1 can connect the same way — the server publishes standard discovery metadata:
For development tools that pass headers directly (e.g. Claude Code, MCP Inspector, custom agents), you can skip OAuth and authenticate with a Business API key instead:
API-key connections always carry full read + write access.

​
Let your coding agent set it up

Coding agents (Claude Code, Cursor, and similar) can configure the connection themselves — paste this prompt:
Only do this in tools you trust with your API key, and use a dedicated key you can revoke from Dashboard → API if needed.

​
Create a reward with an image

Rewards, promotions, raffles, and levels all support images, and the connector can attach them. If you have a hosted image (your website, a CDN, a design tool’s share link), one prompt does everything:
“Create a ‘Free smoothie’ reward for 1,500 points and use this image: https://mysite.com/images/smoothie.png”
The assistant creates the reward and attaches the image in one go. See the images guide for AI-generated artwork and the base64 upload flow.

​
Permissions and security

At the consent screen you grant two scopes:
  • read (View) — view customers, balances, rewards, promotions, raffles, levels, reviews, transactions, devices, and code-batch stats.
  • write (Manage) — issue/deduct points, complete redemptions, and create/update/delete rewards, promotions, raffles, levels, code batches, and the review questionnaire.
If you approve only read, write tools politely refuse. All Business API protections still apply: your assistant can only ever see your own business, all inputs are validated server-side, rate limits are enforced per connection, and points issued through the connector are billed exactly like PTS or API transactions.
Access tokens expire after 1 hour and refresh automatically. Revoking a connection immediately invalidates its tokens.