Marketing & Social Media · Piggy + Claude
Piggy MCP with Claude: Automate Loyalty Rewards and Cashback for Online Stores
The short answer
Claude connects to Piggy through the Model Context Protocol (MCP), an open standard that lets Claude securely read and act within the tool. Using an API key, Claude can typically check customer points, issue cashback and trigger rewards, with permissions set by your organisation and people approving consequential actions.
What is Piggy?
Piggy is a loyalty and cashback platform for online stores. Shoppers earn points or discounts on their purchases, and the store uses these rewards to encourage repeat buying. Piggy is used by e-commerce managers, retention teams and customer experience leaders who want to keep customers returning. It helps businesses track points, manage rewards and build long-term customer relationships without manual effort.
How Claude connects to Piggy through MCP
The Model Context Protocol (MCP) is an open standard that works like a universal adapter. It lets Claude use other software securely, reading information and taking actions, with permissions your organisation controls. Once Piggy is connected, Claude can work with its data in plain language rather than requiring someone to navigate every screen.
Once connected, Claude can typically look up a customer's points balance, review recent cashback, and help prepare or issue rewards according to the rules you set. It can also answer shopper questions through a chatbot, such as how many points they have or how to redeem them.
Access is controlled through an API key with least-privilege permissions, so Claude only sees and does what you allow. Consequential actions, such as issuing large cashback amounts, can require human approval before they run, and every action is logged so your team stays in charge.
What you can automate
Customer points enquiries
Shoppers often ask how many points they have or when they can redeem them. Claude can answer these questions in your chat channel by checking the customer's balance in Piggy and explaining the rules in plain language. This reduces repetitive tickets for your support team and gives customers an instant answer at any hour.
Automated cashback for loyal customers
Marketing teams can set rules for rewarding milestones, such as a customer's fifth order. Claude can identify eligible customers and prepare cashback for approval, so the team reviews the list before payouts go out. This keeps rewards consistent and timely without manual checking of every order.
Retention campaign support
Retention managers can ask Claude to find customers who have not ordered in several months but still hold unused points. Claude can summarise these groups and suggest engagement messages. Your team then reviews and sends the campaign, helping bring lapsed shoppers back.
Points reporting for management
Leaders often want to know how loyalty is performing. Claude can pull points activity and redemption trends from Piggy and present a clear summary in everyday language. This saves time on spreadsheets and helps decision-makers see which rewards are driving repeat purchases.
Support for high-value customers
Customer service teams can use Claude to review a valued customer's loyalty history before a call or email. Claude can highlight recent rewards and open balances so the agent can respond with context and care. Agents keep full control of any reward decision.
An end-to-end workflow: Post-purchase reward and welcome message
TriggerA customer completes an order on the online store.
The store's order system sends the order details to Claude.
Claude checks the customer's history and loyalty status in Piggy through the connected API key.
Claude calculates the points or cashback earned and prepares the reward according to your rules.
A team member reviews any reward above the agreed threshold and approves it.
Claude drafts a personalised confirmation message showing the new balance, which is sent through your email platform.
The approved reward and message are recorded in the audit log.
OutcomeCustomers see their rewards confirmed quickly, which encourages the next purchase. Your team spends less time on manual reward checks while keeping approval control over larger amounts. Results vary by business, but many teams find this improves repeat purchase rates over time.
How we set it up
Free automation audit
We review your store's current loyalty process and identify the workflows most worth automating, such as reward issuing, points enquiries and retention campaigns.
Secure connection with an API key
We connect Claude to Piggy using an API key, configured with least-privilege access so Claude can only perform the actions your business approves.
Workflow design
We design the end-to-end workflow across Piggy and your other systems, such as your online store, email platform, CRM or helpdesk, with human approval points for consequential actions.
Testing and launch
We test the workflow against real past orders and customer cases, then launch with monitoring and audit logs so every action can be reviewed.
Team training
We train your marketing, customer service and operations staff to use the new workflows confidently and to manage approvals and exceptions.
Who benefits
- E-commerce manager
- Runs loyalty programmes with less manual work and clearer reporting on what drives repeat purchases.
- Retention marketing lead
- Identifies lapsed customers with unused points and supports targeted campaigns.
- Customer service manager
- Gives agents instant, accurate answers about points and rewards, reducing repetitive tickets.
- Finance or operations head
- Gains a clear audit trail of cashback issued and approvals given.
Security and control
- Access uses an API key with least-privilege permissions, limited to the actions you approve.
- Consequential actions, such as large cashback payouts, require human approval before they run.
- Every action Claude takes is logged so your team can review and audit it.
- Sensitive customer data is handled only as needed for the task and is not used beyond your workflow.
- We test workflows against real cases before launch and monitor them afterwards.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host their Claude workflows in their chosen region to meet local data expectations. Businesses in India must comply with the Digital Personal Data Protection Act, 2023, and we design workflows and hosting to support it. Organisations in the UAE and Saudi Arabia are subject to their own data protection laws, and we select hosting regions to meet those requirements. The hosting region is chosen during design to meet your specific legal needs.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Piggy MCP server do?
The Piggy MCP server acts as a secure bridge between Claude and your Piggy account. It lets Claude read loyalty information, such as points balances and reward history, and take approved actions, such as preparing or issuing cashback. The server works within the permissions you set, so Claude only reaches the data and actions you allow.
Is connecting Piggy to Claude secure?
Security is built into the setup. Access is granted through an API key with least-privilege permissions, which limits Claude to specific tasks. Consequential actions can require human approval, and every action is logged for review. We also test the connection before launch and monitor it afterwards.
What can Claude do with Piggy?
Typically, Claude can check a customer's points balance, review cashback history, answer loyalty questions from shoppers, summarise programme performance and help prepare rewards for campaigns. The exact actions depend on the access you approve and the rules of your loyalty programme.
How long does setup take?
Setup time depends on how many systems are involved and how complex your reward rules are. A typical project moves from the free audit to launch in several weeks, including testing and team training. We agree a timeline with you after the audit.
What account and permissions are needed?
You need an active Piggy account and an API key that your organisation is permitted to create and manage. We recommend a dedicated key with only the permissions your workflows need. Your Piggy plan and its features determine what is available, so we confirm these during the audit.