Agentic integration by MCP: operates orders and customers in natural language

Loyalty and operations teams are increasingly automating with AI agents: campaigns that create orders, scripts that adjust point wallets, assistants that consult the catalog before launching a promo. Until now, this involved manually integrating the REST API, handling idempotency, and memorizing endpoints. TPP Ops closes that gap with an MCP (Model Context Protocol) server that wraps the public API /api/v1/* as tools that an agent can invoke in natural language.

It is not a second API nor a different access to the internal backoffice. It is a protocol adapter: each MCP call translates into an HTTP request to the API that partners already use, with the same bearer, the same scopes, and the same sub-brand rules. If the token cannot create orders, the tool returns forbidden — the agent cannot bypass authorization.

What a connected agent can do

The tools are automatically generated from the API's operation log. When we add a new endpoint, it appears as an MCP tool without extra work. The catalog covers the operational cycle that matters to integrators and product teams.

• Clients: list, create, update, query currencies, and adjust balances (bulk_adjust_customer_coins included).

• Orders: reserve_order, list, query details, cancel_order and manage shipping.

• Catalog: stores, catalogs, and search_products with masked prices.

• Sessions: create_store_session for player SSO hand-off.

Authentication and scope

The MCP server does not store its own credentials. It takes the header Authorization: Bearer of the incoming request — your API key tpp_live_* or tpp_test_* — and forwards it as is to the API. The key is scoped to a sub-brand: the agent only sees and touches data from that tenant. The provider veil, rate-limit, auditing, and idempotency are inherited from the wrapper withApiKey; the MCP does not reimplement business logic.

Principle of least privilege: create a key with only the scopes that the agent needs. A read-only token cannot write even if the prompt requests it — the API responds 403 and the agent receives an actionable error with the missing scope.

Idempotency in money operations

Endpoints that move money or create clients require Idempotency-Key. An agent that retries out of doubt could duplicate a charge without a stable key. The MCP automatically generates a UUID per call and exposes an optional argument idempotency_key for deliberate retries: the API returns the same cached response with Idempotent-Replay: true.

How to connect it

In the TPP Ops back office, go to Sub-brand → API keys and create a token with the minimum scopes. In ChatGPT (Developer Mode), add a custom connector with URL https://<your-domain>/api/mcp and API key / Bearer authentication. Claude, Cursor, and n8n use the same URL and header.

The human guide lives in /api/v1/mcp; the machine-readable manifest with JSON-Schema for each tool, in /api/mcp/tools — the MCP equivalent of OpenAPI. ChatGPT executes tools/list upon connecting and can already operate: "create an order for this customer", "how many coins does the VIP segment have?", "search for gaming gifts in the catalog".

Why MCP and not just REST

REST is still the option for classic server-to-server integrations. MCP unlocks the same backend for agentic flows: rapid prototyping, AI-assisted operations, connectors in ChatGPT without writing your own middleware. A single source of truth, two ways to consume it.

The server is stateless (Streamable HTTP), scales horizontally without Redis, and is deployed with the same app in POST /api/mcp. If you are already operating loyalty with TPP and want your agents to create orders, check stock, or adjust coins without hitting curl, MCP is the missing layer.