SIGNALS Loyalty Agent Platform
Let an agent manage loyalty programs, rewards, and member operations through SIGNALS with human-in-the-loop approval on sensitive actions.
Overview
global.signals/signals-mcp is an MCP server for the Grow phase that exposes 63 loyalty and member-operation tools with required API auth and HITL approval.
What is this MCP server?
- 63 MCP tools for loyalty, rewards, and member operations
- Human-in-the-loop (HITL) approval path for gated actions
- Bearer Authorization required on remote MCP (mcp_live API key)
- Streamable-http endpoint at https://signals.global/mcp
- SIGNALS Loyalty Agent Platform with GitHub source at psxio/SIGNALS
- HITL approval supported
- Required Bearer Authorization header
What problem does it solve?
You want agents to help run loyalty and rewards programs but cannot risk unattended mutations to member balances or campaigns.
Who is it for?
Solo builders and small teams operating a SaaS or commerce product with an existing SIGNALS loyalty stack who want MCP-driven admin and lifecycle automation.
Skip if: Products without a SIGNALS account and API key, teams that need only generic email marketing, or builders who refuse hosted third-party loyalty infrastructure.
What do I get? / Deliverables
After configuring the Bearer token remote MCP, your agent can call SIGNALS tools for loyalty ops while routing sensitive steps through human approval.
- 63-tool loyalty and member MCP surface in your agent
- Authenticated remote connection to signals.global/mcp
- Agent-assisted lifecycle ops with approval guardrails
Recommended MCP Servers
Journey fit
Loyalty and retention mechanics sit in Grow once you have a product and need repeatable member lifecycle automation. Rewards, tiers, and member ops are lifecycle work—this MCP targets ongoing customer relationship tooling, not greenfield frontend code.
How it compares
Hosted loyalty-platform MCP with 63 tools and HITL gates, not a local brainstorming or planning skill.
Common Questions / FAQ
Who is global.signals/signals-mcp for?
Developers and operators using SIGNALS who want Claude, Cursor, or Codex agents to assist with rewards, members, and loyalty workflows under API control.
When should I use global.signals/signals-mcp?
Use it in grow when you are automating retention, tier changes, or reward campaigns and need MCP tools plus human-in-the-loop approval on risky operations.
How do I add global.signals/signals-mcp to my agent?
Add the remote MCP URL https://signals.global/mcp with the required Authorization header set to Bearer plus your SIGNALS MCP API key (mcp_live_…).