MCP Server
The Loyal Guru MCP Server (Model Context Protocol) is how the Company’s own AI — Cursor, Claude, an internal assistant, or another MCP-capable tool — talks to Loyal Guru with the same Company context Owner already uses.
It is not a second checkout engine and it is not the Owner header chat. For product context see Connect Your agents in the Agentic layer. The MCP Server is for the Company’s AI stack connecting as an integration.
POS, e-commerce, and cart evaluation stay on the Streaming API. Use the MCP Server when you want an external agent to work on loyalty and promotions, not to price a cart at the till.
What you can do
In general, a connected agent can:
| What it is for | |
|---|---|
| Read | Look up the Company’s loyalty and promo context — customers, catalog, locations, campaigns, coupons, and vouchers — so answers stay grounded in this tenant, not a generic model. |
| Act | Help create or adjust operational work you would otherwise do by hand — for example draft a discount or a points campaign, then let a person review and save. |
A person stays in the loop for anything that goes live. The MCP Server does not send personalized coupons to shoppers. That product is AI 1-to-1 Delivery.
Loyal Guru is still the source of truth for eligibility and campaign rules. The MCP Server uses the same Company governance as the rest of the platform.
Access
The MCP Server is not enabled from a self-serve toggle in Owner.
Contact your CSM to use it. They confirm the Company is in scope, enable access, and share how to connect your AI tool.
Do not treat this page as a technical contract. Connection details are provided when access is granted.