Loyalty MCP Server

Plug any agent into your loyalty stack.

One Model Context Protocol endpoint exposes members, points, campaigns, and wallet as safe, governed tools. Connect Claude, Cursor, or your own agent — every call permissioned and logged.

5 governed tools100% auditedOAuth + scoped keys
Loyalty MCP Server
mcp://loyalty.juicysuite.com
Exposed tools · 5
members.search
query + segment members
points.adjust
grant / deduct points
campaigns.create
build & schedule
wallet.push
send pass updates
rewards.issue
mint reward codes
Tool-call logsession live
→members.search { tier: "VIP", region: "HK", inactive_days: 30 }
←1,204 members
→campaigns.create { name: "Win-back VIP", reward: "dessert" }
✓created · id camp_8842
→wallet.push { campaign: camp_8842, audience: 1204 }
✓queued · delivers 09:00 HKT
Connect from Claude, Cursor, or your own agent.
Built for developers

A loyalty API your agent already understands.

01Mon 9am

Tools, not endpoints

members.search, points.adjust, campaigns.create, wallet.push and rewards.issue arrive as typed MCP tools with schemas — no REST plumbing to hand-roll.

02spots it

Permissioned by design

Mint scoped keys per agent and per environment. Grant read-only, draft-only, or full execution — and revoke in one click.

031-tap

Every call audited

A complete, immutable tool-call log — arguments, results, latency, and actor — streamed live and exportable to your SIEM.

04ask it

Bring your own agent

Works with any MCP-compatible client — Claude, Cursor, or an in-house orchestrator. Point it at the endpoint and go.

See it in action

Watch an agent operate your program live.

Connect a client and the tool-call log fills in real time — search, create, push — all governed and reversible.

Loyalty MCP Server
mcp://loyalty.juicysuite.com
Exposed tools · 5
members.search
query + segment members
points.adjust
grant / deduct points
campaigns.create
build & schedule
wallet.push
send pass updates
rewards.issue
mint reward codes
Tool-call logsession live
→members.search { tier: "VIP", region: "HK", inactive_days: 30 }
←1,204 members
→campaigns.create { name: "Win-back VIP", reward: "dessert" }
✓created · id camp_8842
→wallet.push { campaign: camp_8842, audience: 1204 }
✓queued · delivers 09:00 HKT
Connect from Claude, Cursor, or your own agent.
TOOL-CALL LOG

Observe every action as it happens

The live session view shows each tool call, its arguments and result. Replay, diff and revert any action — your loyalty data is never a black box.

Typed tools with JSON schemas
Live, immutable audit stream
Replay & revert any call
JuicySuite AI
agent.juicysuite.com
OO
Our Kowloon VIPs have gone quiet this month. Can you win them back?
Found 1,204 VIPs in Kowloon with no visit in 30 days. They over-index on desserts. Here's a campaign I'd run:
Win-back VIP · KowloonDraft

Double points + a free-dessert reward for VIPs with no visit in 30 days. Auto-sends via wallet push.

Audience
1,204 VIPs
Channel
Wallet · Email
Est. lift
+18%
Ask the agent to build, segment, or schedule…
AGENT CHAT

Or use our agent on top of it

Don't want to build? The Loyalty Marketing AI Agent runs on the very same MCP tools — natural language in, governed actions out.

Same tools, zero code
Natural-language orchestration
Drop in, swap out anytime
Reporting Insight AI
insights.juicysuite.com
Weekly insight · auto-generatedMon 09:00
VIP redemptions jumped 80% after the dessert reward launched.

Kowloon drove most of the lift. At the current pace you'll run out of reward stock by Thursday — restock or cap to protect margin.

+80%
▲ vs last week
ActionRestock dessert rewards (+500) before Thu
INSIGHTS

Feed results straight back

Pipe campaign performance back to your agent through the same endpoint, so it can reason over outcomes and decide the next move.

Performance as a queryable tool
Close the build-measure loop
Composable with your pipelines
How it works

Connected in four steps.

01

Add the endpoint

Point your MCP client at mcp://loyalty.juicysuite.com — discovery does the rest.

02

Authenticate

Mint a scoped key with OAuth. Choose read-only, draft-only, or full execution.

03

Call the tools

Your agent gets typed tools with schemas — members, points, campaigns, wallet.

04

Audit everything

Every call streams to the log and your SIEM. Replay or revert any action.

Use cases

What teams build on it.

ORCHESTRATION

Let an agent run the whole loop.

Search a segment, create a campaign, push to wallet and read back results — all through governed tool calls your agent chains together.

5
tools chained
100%
audited
Loyalty MCP Server
mcp://loyalty.juicysuite.com
Exposed tools · 5
members.search
query + segment members
points.adjust
grant / deduct points
campaigns.create
build & schedule
wallet.push
send pass updates
rewards.issue
mint reward codes
Tool-call logsession live
→members.search { tier: "VIP", region: "HK", inactive_days: 30 }
←1,204 members
→campaigns.create { name: "Win-back VIP", reward: "dessert" }
✓created · id camp_8842
→wallet.push { campaign: camp_8842, audience: 1204 }
✓queued · delivers 09:00 HKT
Connect from Claude, Cursor, or your own agent.
Works with your stack

Speaks MCP — so it speaks to everything.

Any Model Context Protocol client connects in minutes, and the tools reach every loyalty surface underneath.

mcp://loyalty.juicysuite.com
MCP clients
ClaudeCursorClineYour own agent
Exposed tools
members.searchpoints.adjustcampaigns.createwallet.pushrewards.issue
Ops & security
OAuthScoped keysSIEM exportWebhooks
By the numbers

Production-grade from day one.

5
governed tools, typed and discoverable
100%
of tool-calls logged and reversible
<120ms
median tool-call latency
99.9%
endpoint uptime SLA
Frequently asked

About the MCP Server.

Model Context Protocol is an open standard for exposing tools and data to AI agents. The Loyalty MCP Server presents your JuicySuite program — members, points, campaigns, and wallet — as typed tools any MCP-compatible agent can call.

You mint scoped keys per agent and per environment, choosing read-only, draft-only, or full execution. Keys can be rotated or revoked instantly, and every call records the acting key.

Yes. Every tool call is logged with its arguments and result, and state-changing calls are reversible from the audit log — so an agent's mistake is never permanent.

No. The server is agent-agnostic. Use Claude, Cursor, an in-house orchestrator, or our own Loyalty Marketing AI Agent — they all run on the same tools.

Loyalty MCP Server

Give your agents safe hands on your loyalty program.

Grab an API key and make your first governed tool-call in under ten minutes.