About loyaltyvip
loyaltyvip provides JavaScript and TypeScript tools for searching U.S. casino rewards information and accessing a player’s own loyalty records. Its MCP server offers directory lookups without a key and player actions with a personal API key.
Key features
- 01Search the public U.S. casino directory
- 02View casino rewards programs and tiers
- 03Access personal loyalty data
- 04Use stdio or HTTP MCP transport
Use cases
- 01Find casinos by state and rewards availability
- 02Check a casino’s rewards program and tier ladder
- 03Retrieve personal loyalty records with an API key
MCP support
The MCP server exposes casino search, casino details, and rewards-program listing without authentication. Player actions require a personal API key; stdio and Streamable HTTP transports are available.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://loyaltyvip.com/mcpclaude mcp add --transport http justinmont84-loyaltyvip https://loyaltyvip.com/mcp{"mcpServers":{"justinmont84-loyaltyvip":{"type":"http","url":"https://loyaltyvip.com/mcp"}}}Open in Cursor{"servers":{"justinmont84-loyaltyvip":{"type":"http","url":"https://loyaltyvip.com/mcp"}}}Open in VS Code{"mcpServers":{"justinmont84-loyaltyvip":{"type":"http","url":"https://loyaltyvip.com/mcp"}}}{"mcpServers":{"justinmont84-loyaltyvip":{"serverUrl":"https://loyaltyvip.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
5| Parameter | Type | Required | Description |
|---|---|---|---|
| q | string | No | Name search |
| type | string | No | casino_type: commercial | tribal | racino |
| limit | integer | No | |
| state | string | No | Two-letter state code, e.g. NV |
| offset | integer | No | |
| has_rewards | boolean | No |
Details
From the project READMELoyaltyVIP — JavaScript / TypeScript developer tools
Official SDK, CLI, and MCP server for LoyaltyVIP — the privacy-first casino player intelligence platform. Search the public U.S. casino directory (rewards programs + tier ladders) with no key, and access a player's own loyalty data with a personal API key.
- API docs: https://loyaltyvip.com/developers
- OpenAPI 3.1: https://loyaltyvip.com/openapi.json
- Auth guide: https://loyaltyvip.com/auth.md
- Full agent reference: https://loyaltyvip.com/llms-full.txt
Packages
| Package | What it is | Install |
|---|---|---|
@loyaltyvip/sdk | Typed, zero-dependency REST client | npm i @loyaltyvip/sdk |
@loyaltyvip/cli | Command-line interface | npm i -g @loyaltyvip/cli |
@loyaltyvip/mcp | Model Context Protocol server (stdio) | npx -y @loyaltyvip/mcp |
Quickstart (SDK)
import { LoyaltyVIP } from "@loyaltyvip/sdk";
const lv = new LoyaltyVIP(); // no key needed for the public directory
const { data } = await lv.searchCasinos({ state: "NV", has_rewards: true, limit: 5 });
console.log(data.map((c) => c.name));
// Your own data needs a key (https://loyaltyvip.com/dashboard/developer):
const me = new LoyaltyVIP({ apiKey: process.env.LOYALTYVIP_API_KEY });
console.log(await me.player("tier_status"));
CLI
npx @loyaltyvip/cli casinos --state NV --rewards
npx @loyaltyvip/cli casino bellagio-nv-880e8400
LOYALTYVIP_API_KEY=lvip_live_... npx @loyaltyvip/cli tiers
MCP server
Add to your MCP client (e.g. Claude Desktop):
{
"mcpServers": {
"loyaltyvip": {
"command": "npx",
"args": ["-y", "@loyaltyvip/mcp"],
"env": { "LOYALTYVIP_API_KEY": "lvip_live_..." }
}
}
}
The key is optional — directory tools (search_casinos, get_casino, list_rewards_programs) work without it. player_action needs a key. An HTTP (Streamable) MCP transport is also live at https://loyaltyvip.com/mcp.
Develop
npm install
npm run build # builds sdk -> cli -> mcp
License
MIT © movaMedia. LoyaltyVIP is independent and not affiliated with any casino brand. It is a record-keeping and analytics tool — not a gambling product.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.