The TRYB Loyalty MCP server lets your AI assistant talk to your TRYB Loyalty account directly.
Once connected, you can manage customers, loyalty cards, card templates, balances, and automation workflows by simply asking — in Claude, Cursor, VS Code, or any other MCP-compatible client.
It speaks the Model Context Protocol over Streamable HTTP and authenticates either by signing in with your TRYB Loyalty account (OAuth) — the recommended way — or with a personal API key.
What you can do once connected
Customers & segments — create, find, update, and delete customers; list segments.
Templates — create card templates and manage reward tiers, membership tiers, and feedback links.
Cards — issue cards, look them up, update fields, and set expiration and membership tier.
Balances — add or subtract stamps, points, scores, visits, amounts, purchases, and rewards; redeem coupons.
Locations — create and manage store locations.
UTM links — create and manage UTM tracking links and read their reward and enrollment stats.
Workflows — build, activate, pause, run, and inspect automation workflows and their logs.
External services — connect and manage third-party integrations.
White-label — manage custom domains, branding, and sub-account menus for white-label setups.
Agencies — search sub-accounts and act on their behalf on Agency plans.
Property
Value
Server URL
https://api.trybloyalty.com/mcp
Transport
Streamable HTTP
Authentication
OAuth 2.1 (recommended) or Authorization: Bearer <YOUR_API_KEY>
Method
POST
Using a white-label or custom domain? Replace api.trybloyalty.com with your own API host everywhere below (for example https://api.your-brand.com/mcp). Sign-in works the same on any domain — each host is its own issuer.
A TRYB Loyalty Business Plan account that includes API access.
An MCP-compatible client such as Claude Desktop, Claude Code, Cursor, or VS Code.
Node.js is only needed for the API-key setup on Claude Desktop (the mcp-remote proxy). The OAuth setup needs nothing extra.
There are two ways to authenticate. Pick one:
Sign in with OAuth (recommended) — no key to copy. Point your client at the server URL, then sign in with your normal TRYB Loyalty login in the browser and approve access. Your client registers itself automatically and refreshes its access for you.
API key — send a personal Bearer token with every request. Best for clients without OAuth support, scripts, and automation.
You give your client just the server URL. On first use it opens a browser, you log in to TRYB Loyalty and approve access, and the assistant is connected — no API key to copy or store.
Claude Code
Claude Desktop / Claude.ai
Cursor
VS Code (Copilot)
Other clients
Run this command in your terminal:
Copy
claude mcp add --transport http tryb https://api.trybloyalty.com/mcpThen run /mcp, select tryb → Authenticate, and a browser window opens for you to sign in and approve. Verify with claude mcp list.
Permissions. When you approve access, the assistant is granted two scopes: mcp:read for read-only tools, and mcp:write for tools that create, update, or delete data.
Use this for clients that don't support OAuth, or for scripts and automation.
Log in to your TRYB Loyalty dashboard.
Open Settings → API.
Copy your personal API key.
Your API key grants full access to your account.
Treat it like a password. Never share it. Never commit it to a public repository. Rotate it immediately if it leaks.
Pick your client below and add the configuration.
Replace <YOUR_API_KEY> with the key from the previous step.
Claude Code
Claude Desktop
Cursor
VS Code (Copilot)
Other clients
Run this command in your terminal:
Copy
claude mcp add --transport http tryb https://api.trybloyalty.com/mcp \
--header "Authorization: Bearer <YOUR_API_KEY>"Verify it with claude mcp list.
After connecting, ask your assistant:
Use the whoami tool and tell me which account I'm connected to.
If the connection works, it returns your company name, tariff, currency, and locale.
You can also ask it to list your card templates or list your customers to confirm the tools work end to end.
If your account is on an Agency or Agency Partner tariff, you also get tools to work across sub-accounts:
search_companies and get_company — find and inspect sub-accounts and referrals.
impersonate_company — switch the session to act on behalf of one sub-account.
stop_impersonation — return to your own agency context.
Impersonation is session-scoped and expires automatically after 1 hour.
Prefer OAuth — no long-lived secret is stored in your client's config files.
If you use an API key, store it in an environment variable or your client's secret store.
Use a dedicated key for AI assistants so you can rotate it independently.
Rotate the key immediately if you suspect it has been exposed.
Symptom
Likely cause and fix
Browser sign-in doesn't finish
Make sure you're logged in to the correct TRYB Loyalty account in that browser, then retry. Remove and re-add the server to restart the flow.
401 Unauthorized
With OAuth, re-run the sign-in. With an API key, the key is missing, mistyped, or your plan does not include API access — re-copy it from Settings → API and confirm your tariff.
Tools do not appear
The client was not fully restarted. Quit and reopen it. For Claude Desktop, quit the app completely.
npx or mcp-remote errors
Node.js is not installed or is not on your PATH. Install Node.js and try again. (Only the API-key Claude Desktop setup needs it.)
Connection works but actions fail
The action may not be available on your tariff, or a required field may be missing. Check the returned error message for the server response.