Design
getleal.com
Extracts business brand kits and lets users design, preview, and manage Leal loyalty cards and store setups.
ENDPOINT 1
https://mcp.getleal.com/mcp
MCP server metadata
- Name
- leal
- Version
- 1.0.0
Leal runs digital loyalty stamp cards for independent shops, cafés and salons: customers keep the card in Apple Wallet or Google Wallet and staff stamp it with the Leal app. Use these tools to set up and change a store's loyalty programme. A typical setup: get_brand_kit on the business's website, preview_card_designs with two or three designs built from its colours and logo, then (after the person picks one) create_card with a reward, create_poster for the counter, and create_location. To set up a new business, client or demo alongside the stores a login already has, create_store first and pass its store_id to the other tools; never put another business's card into an existing store. get_brand_kit, list_design_options and preview_card_designs work without an account; the others ask the person to sign in or create a free Leal account the first time. Leal's free plan has one card with one reward, one poster and one location. Deleting, billing and customer data are managed in the Leal app.
Known tools 15
get_brand_kitReads a business's public website and returns its name, a colour palette (with where each colour was found; colours read from the logo are the most reliable, and website-builder default colours are filtered out), logo and icon image URLs, a hero image, a guess at the type of business, and a suggested starting card design built from those.
Inferred read-onlylist_design_optionsLists what a Leal loyalty card can look like: stamp icons, preset strip photos, limits, and how the pass is laid out on Apple and Google Wallet.
Inferred read-onlypreview_card_designsRenders one to four loyalty card designs as Apple Wallet and Google Wallet passes so the person can compare them and pick one.
Inferred read-onlylist_storesLists the Leal stores this login can manage, with each store's id, plan and how far through setup it is, and the agencies it can add new stores to with create_store.
Inferred read-onlyget_store_setupShows a store's setup checklist (store details, card, poster, first customer, staff app), plan limits and usage, and its cards with rewards, locations and posters.
Inferred read-onlyget_cardShows a saved loyalty card's design and rewards, with an Apple and Google Wallet preview.
Inferred read-onlycreate_storeAdds a new, empty store to the login's agency, with its own cards, posters and locations: for a client, a second business, or a demo to show a prospect.
Inferred read-onlyupdate_storeSets a store's public name and logos, which Leal uses on cards, posters and signup pages.
Inferred read-onlycreate_cardSaves a loyalty card design and its rewards to a Leal store, ready for customers to add to Apple Wallet or Google Wallet.
Inferred read-onlycreate_rewardAdds a reward that customers can redeem with stamps from a card, e.g.
Inferred read-onlyupdate_rewardChanges a reward's name, stamps needed or description, or turns it off.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.leal]
url = "https://mcp.getleal.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"leal": {
"type": "http",
"url": "https://mcp.getleal.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: leal
Remote MCP URL: https://mcp.getleal.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"leal": {
"url": "https://mcp.getleal.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"leal": {
"type": "http",
"url": "https://mcp.getleal.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "leal",
"transport": "streamable-http",
"url": "https://mcp.getleal.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.