Model Context Protocol

Your Loyalty Program, Inside the AI You Already Use

Connect your account to Claude, Cursor or Copilot once, then ask for things in plain language — issue a card, add points, read a segment, pause a workflow. Nothing to install, no key to keep safe, and it comes with the Business plan.

See it work

Ask for It Instead of Clicking for It

Pick a question. The reply you see is written for this demonstration and the figures are made up — but every tool it calls along the way is one the connection really has.

Your AI assistantConnected
What it can reach

Ten Parts of Your Account, Not All of Them

The connection exposes a fixed set of tools. Anything outside this list still happens in the dashboard, where you can see what you are doing.

Customers and segmentscreate · find · update · delete · list segmentsLook someone up by phone or email, fix a misspelled name, or read how many people sit in each RFM segment right now.
Card templatescreate · update · activate · reward tiers · membership tiersSpin up a card, set its reward or membership tiers, attach a feedback link, and switch it on. The artwork itself stays in the dashboard.
Cardsissue · look up · update · set expiry · set tier · deleteHand a card to a customer, check what is on one, move somebody up a membership tier, or change when a card runs out.
Balancesstamps · points · visits · amounts · purchases · rewards · couponsAdd or take off anything a card holds, hand over a reward, redeem a coupon, or restore the visits on a membership.
Messagessend push · send SMS · list what went out · auto-push rulesSend a push or an SMS, read what has already gone out, and build the automatic pushes that fire off a card’s own events.
Locations and promotionscreate · update · delete · listAdd a branch with its geo-push point, or switch which campaigns are running without opening the dashboard.
Links, stats and revenueUTM links · install stats · reward stats · revenueMake a tracking link for a poster or an ad, then ask which ones brought sign-ups, which brought rewards, and what came of it.
Workflowsbuild · activate · pause · run · read logsStart, stop or inspect an automation, and read its logs to find out why a message did or did not go out.
Your teamadd · update · remove · read permissionsCreate a manager seat for a new member of staff, check what an existing one is allowed to do, or close an account that has left.
Webhookscreate · list · deletePoint your own systems at the events coming out of your program, without going hunting through settings for the form.
Two things it is the wrong tool for. Designing a card is one — colors, logo and layout want eyes on them, and that lives in the dashboard. Importing a long customer list is the other: the connection is paced at ten requests a second, so a thousand rows typed into a chat window will stall long before they finish. Use the import in your dashboard for that.
Setup

One Address, Pasted Once

Every client below connects to the same address. Signing in through your browser is the route we recommend — nothing to install, and no key to keep safe.

Server address https://api.loyaltyperfect.com/mcp
The other route

Or use an API key

If your client cannot do the browser sign-in, you can send a personal key instead. Find it under Settings → Integrations on the Business plan, and pass it as a bearer token in the Authorization header.

  • It is the whole accountA key carries full access — there is no read-only version of it. Browser sign-in gives the assistant a read scope and a write scope instead.
  • Keep it out of the filePoint the config at an environment variable rather than pasting the key itself, so it never sits in a file you might share.
  • Some clients need Node.jsDesktop apps with no header field reach the server through a small proxy, and that proxy needs Node.js installed. The browser route does not.
Before you let it loose. Once it is connected, your AI client lists every tool the server carries, split into the ones that only read and the ones that can write or delete, and both lists start out asking your approval before anything runs. You can tighten any single tool to always ask, or block it outright. One thing to watch: an assistant running in its automatic mode judges that for itself and may act without asking, even on a tool you marked as needing approval. Leave it on manual approval until you have watched it work a few times.
Worth knowing

Four Things We Will Tell You Up Front

None of them stop this from being useful. All of them are better known before you connect anything.

It needs the Business plan

The connection runs on API access, and the API comes with the Business plan. On Start and Grow, the Workflow Builder in your dashboard is the way to automate — it is on every plan.

It changes things, not just reads them

Most of the tools it carries can write or delete, not just read. Points go on cards, workflows stop, customers get deleted — and pushes and text messages go out to real people. Ask for one thing at a time and read the reply before saying yes to the next, the same way you would with anyone new behind your counter.

The assistant is not ours

You bring your own Claude, Cursor or Copilot subscription, and that conversation — including whatever customer details come back — goes to whoever makes it. Their privacy terms apply to that half, not ours.

Ten requests a second

That is the ceiling, and it cannot be raised. Plenty for asking questions and fixing one card at a time; not enough for moving a whole customer list through a chat window.

Connect It Once, Then Just Ask

It is on the Business plan, alongside the API, webhooks and the automation tools. The trial runs fourteen days and needs no card. Choose the Business plan when you start it, and you can see whether talking to your program beats clicking through it.