Loyalz MCP server

What the server gives an agent

Most marketing MCP servers hand an assistant one ad account. Loyalz is the layer that already holds every connected ad platform next to the store's settled orders, the loyalty programme the store runs, and the creative pipeline that feeds the ads. The MCP server exposes all three through one connection, scoped to one merchant account:

• Insights — query spend, clicks, conversions, revenue, orders, POAS/ROAS and every calculated metric across Meta, Google, TikTok, LinkedIn, WooCommerce, Shopify, Sellasist and e-mail; build and edit dashboards; define custom metrics from formulas.
• Loyalty — read and shape the programme (levels, quests, tasks, benefit collections, leaderboards), grant points, cashback or benefits to a named customer, read the ledgers.
• Creative Studio — brand profile and references, concept runs for statics and video with a human review gate on prompts, ad copy, approvals, and publishing approved creatives into an existing Meta ad set as paused ads.

Prompts that work on day one

• "Compare Meta and Google spend against store revenue for the last 30 days, by week, and tell me which channel has the better POAS."
• "Add a KPI card with blended CAC to the Weekly dashboard."
• "Create a quest worth 200 points for customers who follow us on Instagram."
• "Show the three best-performing ads in our summer campaign and draft a static concept run from the winner."

Connect

You need a Loyalz merchant account and an MCP token. Tokens are created in the merchant panel under Settings → Agents API; each token is bound to one merchant and can be revoked there at any time. Send it as a Bearer header on the SSE request and on every message. Tokens in the URL are not accepted.

Claude Code

claude mcp add --transport sse loyalz https://api.loyalz.io/api/mcp/sse --header "Authorization: Bearer <token>"

Claude Desktop, Cursor, Windsurf and other mcpServers clients

{
  "mcpServers": {
    "loyalz": {
      "type": "sse",
      "url": "https://api.loyalz.io/api/mcp/sse",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Any MCP client or SDK

GET https://api.loyalz.io/api/mcp/sse
Authorization: Bearer <token>
Accept: text/event-stream

# the server advertises the messages URL in the first event;
# POST every JSON-RPC message there with the same Authorization header

After connecting, call tools/list once. The catalog below is what it returns. Every tool takes an input object, including reads with no fields ({"input": {}}).

Claude.ai and ChatGPT connector directories

The hosted directories of Claude and ChatGPT sign users in with OAuth 2.1 and expect the Streamable HTTP transport; a static token in a header is accepted by Claude Code, Claude Desktop, Cursor, Windsurf, the SDKs and self-hosted agents, but not by those two directories. OAuth sign-in and Streamable HTTP for the Loyalz server are in progress. Until they ship, connect through a header-capable client as shown above; this page will name the directory entries the day they are live.

Authentication, tenancy and audit

• One token, one merchant. The connection context is the merchant that owns the token. No tool takes a merchant id, a user id or a "switch account" argument; to work on another account, connect with that account's token.
• Bearer only. The token travels in the Authorization header of the SSE request and of every POST to the messages endpoint. Session URLs are not credentials and a session cannot outlive its token: revocation is checked again before each tool call.
• Plan gates apply as in the app. Insights tools need Insights enabled on the account; Creative Studio tools need the Shark plan or higher. A gated call returns a clear refusal with the plan required, never partial data.
• Writes are idempotent. Tools that change state or spend credits take an idempotency_key; a retried call with the same key returns the original result instead of acting twice.
• Audit. Actions taken through the server are logged per merchant and readable with get_mcp_history. Studio and publishing keep their own operation registers.

Tool catalog

77 tools · 43 in Creative Studio · generated from the server registry on 23 September 2026

read no state change   writes changes data in your account   spends credits charges Studio credits or reserves them

What can go wrong, and what cannot

• Money. No tool moves money or changes a subscription. Studio steps marked "spends credits" draw on prepaid credits; studio_list_credit_packs only returns checkout links, it never purchases.
• Ads. studio_publish creates ads in an existing Meta ad set in a paused state; nothing goes live without a human switching it on in Ads Manager. Read tools never touch the ad account.
• Customers. Granting points, cashback or benefits changes a real customer's balance and is logged with the reason you pass. Use idempotency keys.
• Data. Tool responses contain your account's marketing data, order aggregates, customer e-mails on the loyalty ledgers and creative assets. Whatever your AI client does with a tool response is governed by that client's own policy; Loyalz does not send your data to any model vendor as a side effect of a tool call.
• Limits. Studio calls that trigger vision or generation work are throttled per account; a throttled call returns a retry hint instead of failing silently.

For directory reviewers and integrators

• First-party API. The server runs on api.loyalz.io, the same backend that serves the Loyalz merchant panel. No third-party data is proxied; every tool reads or writes the merchant's own Loyalz account.
• Accounts and plans. A merchant account is required (book a demo to get one). Insights tools need Insights enabled on the account; Creative Studio tools need the Shark plan. A fully provisioned test account can be issued for review on request to majewski@loyalz.io.
• Read and write are separate tools. There is no catch-all request tool; each tool does one thing and is marked above as read, writes, or spends credits. Writes take an idempotency key.
• Side effects with money or reach. Studio generation tools spend prepaid credits. studio_publish creates paused ads only. Nothing moves money, changes a subscription or sends messages to customers.
• Known limitations. One merchant per token; no account switching inside a session. Studio vision and generation calls are throttled per account. Ad-platform data is as fresh as the last sync (daily, with intraday syncs for the store).
• Categories. Marketing analytics · Advertising · E-commerce · Loyalty and CRM · Creative production.

Privacy, terms and support

• Privacy policy: loyalz.io/legal/privacy/
• Terms: loyalz.io/legal/terms/ and terms for brands
• Deleting your data, including Meta data: loyalz.io/legal/data-deletion/
• Support and listing questions: majewski@loyalz.io; privacy matters: privacy@loyalz.io
• Status of the server: this page is updated when the catalog changes; the current build answers tools/list with 77 tools.

Changelog

• 2026-09-23 — Creative Studio (43 tools) added; authentication is header-only, the ?token= query parameter was retired; catalog now 77 tools.
• 2026-07-17 — Insights tools: metric catalog, query engine, dashboards and calculated metrics.
• 2026-06 — First public version: loyalty programme tools.

Get a merchant account Read: why one MCP for ads and the store