Business operationsPublic source

Loyalty MCP Server

A loyalty-program layer for ADK-Rust Enterprise agents. 18 MCP tools over members, a points ledger, tiers, a rewards catalog, redemptions, and promotional offers — for membership, points-balance, and rewards agents.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides loyalty capabilities through a typed MCP contract.

Architecture

How Loyalty MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Loyalty MCP Server

Validates the request and owns 18 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Tool catalog

What can an agent ask Loyalty MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

18 named tools

enroll_member

Enroll a new loyalty member

internal write

get_member

Get a member's account, tier, and balances

read only

find_member

Find members by membership number or name

read only

set_member_status

Change a member's account status

internal write

get_balance

Get points balance and tier progress

read only

earn_points

Earn points from spend (tier + offer multipliers applied)

internal write

award_points

Award points directly (bonus/goodwill)

internal write

adjust_points

Manually adjust points up or down

internal write

expire_points

Expire points from a member's balance

internal write

get_ledger

Get a member's points-ledger history

read only

create_reward

Create a catalog reward

internal write

list_rewards

List active rewards (optionally tier-filtered for a member)

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

11 internal write7 read only

Gated points writes — earn_points, award_points, adjust_points, expire_points, redeem_reward, and set_redemption_status require approval in production (they move points of monetary value);…
Balance integrity — all changes go through the ledger; the balance can never go negative, and cancellations are reversed via compensating entries.
No raw PII — members carry a contact reference, not necessarily raw contact details.
Integration scaffold — the in-memory store is for development; back it with a durable store and bind actors to authenticated identities in production.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Cancellation

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-loyalty

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-loyalty",
    ["mcp-loyalty"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring