Skip to main content
The LoyaltyLion MCP server lets AI assistants — such as Claude, Cursor, or any Model Context Protocol client — answer questions about your loyalty program using live data from your account. Connect it once with an API key and you can ask, in plain language, how your program is configured and how it’s performing.
Merchant MCP is currently in beta. It’s available on the Classic plan and above and must be enabled for your program — contact support@loyaltylion.com to have it turned on.

​
What it can do

The MCP server exposes a small set of read-only tools:
CapabilityWhat the assistant can do
Describe program setupRead your program’s configuration — name, live status, sites, locales, points-expiry policy, earning rules, rewards, tiers, and referral incentive.
Analytics metricsPull time series for a single analytics metric — membership, points, orders, revenue, rewards, and customer lifetime value — over a date range, bucketed by day, week, or month, optionally filtered by site, rule, or reward.
Fetch customersLook up loyalty customers by email, ID (merchant_id), or created/updated time range, with their points balances, enrollment state, tier, and tags.
Fetch ordersList orders by time range, order number, ID (merchant_id), or customer, with each order’s amounts, statuses, timestamps, points earned, and rewards used.
See Example prompts for things you can ask once it’s connected.

​
Endpoint

The MCP server is a streamable-HTTP endpoint served from the same host as the LoyaltyLion API: 
POST https://api.loyaltylion.com/mcp
Authenticate with a Program API key (or OAuth token) passed as a Bearer token in the Authorization header. Site token & secret authentication is not accepted.

​
Set up the MCP server

​
1. Create an API key

Sign in to your LoyaltyLion account, go to Manage > API keys, click Create API key, and follow the steps. The token is shown only once after creation — store it somewhere secure. For more detail on API keys, see Authentication › API keys.

​
2. Choose scopes

The MCP server only ever reads data, and the tools available to a key depend on the scopes you grant it. Grant the read scopes that match the data you want the assistant to access:
CapabilityScope required
Describe program setupNone — any valid key works
Analytics metricsNone — any valid key works
Fetch customersread_customers
Fetch ordersread_orders
Program setup and analytics don’t require a specific scope, so a key with no scopes can use them. To let the assistant look up customers or orders, grant read_customers and read_orders. For the full list of scopes, see the API key scopes reference.

​
3. Connect your client

Add the server to your MCP client’s configuration. Most clients accept an HTTP server entry with an Authorization header. For example: 
{
  "mcpServers": {
    "loyaltylion": {
      "type": "http",
      "url": "https://api.loyaltylion.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Replace the token with your own API key. The exact configuration format varies by client — consult your client’s documentation for where MCP servers are configured and how to supply request headers. Once connected, your client will discover the available tools automatically. Head to Example prompts to start asking questions.