How to connect Claude or ChatGPT to your Leat account (AI Assistant integration)

What it is

The AI Assistant integration lets an AI client such as Claude or ChatGPT read your Leat accounts through the Model Context Protocol (MCP). You ask questions in plain language; the assistant uses Leat's tools to look the answer up in your own data. Nothing in your accounts changes through the connector: it reads. Creating or editing rewards, earn rules, lists, forms and campaigns happens in the Leat dashboard, where the Leat assistant can do it for you.

Before you start

You're an administrator of each Leat account you want the assistant to read.
In each of those accounts, go to Apps → Integrations, search for AI Assistant and click Install.
The integration page shows the connector URL: https://api.leat.com/api/mcp. It's the same for every account.

Connect Claude

In Claude (web, desktop or mobile), open Settings → Connectors.
Add Leat from the directory. If Leat is not listed yet, choose Add custom connector and paste the connector URL.
Claude opens Leat. Sign in with your Leat login if needed.
The consent screen names the application asking for access and lists every account it will be able to read. Check the list and click Allow. With a single account, you also decide here whether the assistant may see personal customer data.
Back in Claude, start a chat and ask, for example, "How is my loyalty program doing?".

Connect ChatGPT

Open Settings in the ChatGPT desktop app.
Select Plug-ins, then open the MCPs tab.
Click Add server, give it a name and select Streamable HTTP.
Paste the connector URL and click Save.
Back in the server list, click Authenticate. Sign in to Leat in your browser, check the accounts and allow access.

You need the ChatGPT desktop app and a paid ChatGPT plan for the MCPs tab to appear.

Which accounts the assistant can read

One connection reaches every account where you're an administrator and the AI Assistant integration is installed and active. This is checked again on every request:

An account where the integration is activated later is added straight away, without connecting again.
Deactivating the integration in an account, or losing your administrator role there, takes that account out straight away.

When a question could be about more than one account, the assistant asks which account you mean. Once you've said, it keeps to that account until you name another. To compare accounts, ask for it.

A connection you made earlier, when the consent screen asked you to pick one account, stays tied to that account. To let the assistant read all your accounts, remove the connector in Claude or ChatGPT and connect again.

Other MCP clients

Any MCP client that supports OAuth can use the connector URL. A client that runs unattended and cannot open a browser can use a personal access token instead: create one on the Auth tab of the integration page and send it as a Bearer token. Such a token belongs to that one account, is valid for 90 days and can be rotated or revoked on the same tab.

What the assistant can see

Everything is limited to the accounts the connection reaches, and to what your own role in Leat may see.

Program: settings, tiers and tier milestones, earn rules, the reward catalog with its visibility filters, promotions, segments, your locations, and the users who have access to the account.
Contacts and transactions: recent orders and their payments; why an order did or did not award points or stamps; why a contact cannot claim a reward; a voucher by its code, including whether it can still be used and where it was redeemed; a gift card by its hash, with balance and transactions; prepaid balances; a contact's stamp cards, or one card by the code on its QR code: the stamps on it, full cards ready to redeem, when the stamps expire, and the stamps and redemptions booked on it; a contact's loyalty standing (points, tier, subscriptions, lists, cards, wallet pass); till sessions for Lightspeed K-Series accounts.
Problems at the till: why a reward, voucher or stamp card can't be redeemed at the till, with the cause, how to fix it and the locations where it failed. For Lightspeed K-Series accounts it also lists which Lightspeed settings to check, in order.
Marketing: email campaigns with their statistics and voucher attribution; recurring emails with their runs and statistics; automated emails with their statistics; automations, what each one does and how it ran; forms and their submissions; the state of your email domains (SPF, DKIM, DMARC) and sender profiles.
Business App: your Business App configurations with the settings each device runs on, and your linked devices with their business profile, app version and when they were last seen. Link codes for new devices are never shown.
Data: your imports and exports, generated batches and notifications, and how they went.
Analytics: aggregate questions over contacts, points transactions, orders, gift card transactions, voucher redemptions, visits and bookings. Results are aggregates, at most 1000 rows.
Help center: the assistant can search these support articles.

What the assistant cannot do

Change anything. The connector has no tool that creates, edits or deletes, so a connected assistant cannot add a reward, change a rule, build a list or send a campaign, whatever you ask it. For those, use the Leat assistant inside the dashboard or the dashboard itself.

Personal customer data

By default the assistant does not see who a contact is. It gets loyalty standing, balances and aggregates, while names, email addresses, phone numbers, birth dates and addresses are withheld, also inside filter definitions.

Sharing personal data is set per account, with Allow access to personal customer data on the Permissions tab of that account's integration page. The tab appears once the integration is installed. When your connection reaches a single account, the consent screen shows the same switch. When it reaches several, the consent screen shows for each account whether it shares personal data, and you change it on that account's Permissions tab. Switch it off again at any time; the next request follows the new setting.

Stopping access

Any of these stops the assistant immediately:

Remove the connector in Claude or ChatGPT. This stops access to all accounts.
Deactivate or uninstall the integration under Apps → Integrations → AI Assistant. This stops access to that account.
Remove the person who approved the connection as administrator of an account. Access is tied to their role and is checked on every request.
For a personal access token: revoke it on the Auth tab.

Security

Sign-in uses OAuth 2.1 with PKCE. The AI client never sees your Leat password.
Access tokens expire after 24 hours and are refreshed automatically while the connection stays approved.
Every request is checked against your current role on the account it reads.
A connection only reaches the accounts where you're an administrator and the AI Assistant integration is active. A request for any other account is refused, even with a valid login.

Troubleshooting

"Couldn't connect" in Claude: check that the integration is active in at least one account you administer, under Apps → Integrations → AI Assistant.
An account is missing: the integration isn't installed or active in that account, or you're not an administrator there. Fix that and the account is added on the next request.
The assistant only reads one account: the connection was made when you picked one account on the consent screen. Remove the connector and connect again.
The assistant asks which account you mean: your connection reaches more than one account. Name the account in your question.
The assistant says a tool is not available: your role in Leat does not include that area, or the integration in that account does not hold that permission.
The assistant says it cannot create or change something: that is by design. The connector reads only; the Leat assistant in the dashboard can make the change.
Numbers do not match the dashboard: ask the assistant which period it counted. Analytics tools answer in whole days in the account's timezone.

Support

Email support@leat.com or use the chat in the dashboard.