Skip to main content
The LoyaltyDog MCP server exposes our REST API as a set of structured tools any Model Context Protocol client can call. It’s an HTTP wrapper around the LoyaltyDog API — no direct database access — and can be pointed at development, staging, or production.

​
What you can do

Once connected, an AI assistant can answer natural-language questions about your loyalty data:
  • “Show me the top ten loyalty programs by active customers this month.”
  • “List gift cards issued in the last 24 hours.”
  • “What’s the wallet-pass install rate for program XYZ?”
  • “Create a new customer record for [email protected] in program ABC.”
The MCP server enforces the same authentication and program-isolation rules as the underlying REST API — it cannot reach data your token does not own.

​
Architecture

The server runs as a local process started by your AI client. Your bearer token never leaves your machine except in outbound calls to the LoyaltyDog API.

​
Tool surface

The MCP server is read-only — it covers listing, getting, and searching the high-traffic parts of the API:
  • Loyalty programs — list_programs, get_program
  • Customers — search_customers, get_customer
  • Loyalty transactions — get_customer_transactions
  • Wallet passes — list_passes, get_pass
  • Gift cards — list_gift_cards, get_gift_card, get_gift_card_transactions
  • System — get_system_health
There are no create, update, issue, redeem, or reporting tools. For writes — creating or updating customers, issuing or redeeming gift cards, regenerating wallet passes, generating reports, and so on — hit the REST API directly. See the API reference.

​
Next steps

Install the server

Clone, configure, and run the MCP server locally.

Connect a client

Wire up Claude Desktop, Claude Code, Cursor, or Windsurf.