SocialHub.AIFlash

AI & Brand · MCP & API

Your retention stack as governed tools AI agents can call.

Loyalty, campaigns, members, and segments — exposed as MCP tools that Claude, Cursor, and Copilot can discover and invoke under your governance. Not brittle REST glue, not API tokens pasted into a chat window.

AI agent → Flash · MCP over JSON-RPC
POST /api/mcp
Authorization: Bearer fl_live_•••
{
"method": "tools/call",
"name": "earn_points"
}
200 · points earned, scoped to your tenant

The problem

Your team is adopting AI agents faster than your stack can safely expose itself to them.

Brittle point-to-point glue

Every new integration means hand-wiring REST calls and maintaining them as endpoints drift.

Ungoverned access

Handing an agent your API means handing it everything — no scopes, no tenant boundary, no audit trail.

Agents can't discover what you do

A REST endpoint is invisible to an AI agent until someone hard-codes it. Capabilities stay locked away.

How it works

14 inbound tools, every call governed.

Flash speaks MCP over JSON-RPC at POST /api/mcp. An agent calls tools/list to discover capabilities, then tools/call to act — each invocation authenticated, scoped, tenant-isolated, and audited.

Inbound MCP tools

14 total
list_membersget_memberearn_pointsredeem_pointsget_points_balanceget_member_tierlist_coupon_poolsget_member_couponsredeem_points_for_couponget_dashboard_stats+4 more

Each tool ships a JSON-Schema input contract and a hard tenant guard. The same capabilities are also exposed as a hand-written OpenAPI v2 REST surface for non-agent integrations.

Authentication

Authorization: Bearer fl_live_••••••••

Keys are stored as a SHA-256 hash with the plaintext shown exactly once. Each carries scopes and can be revoked. The full-access /api/mcp endpoint requires an all-scope key.

One governed path, every agent

Whether the caller is Claude, Cursor, or Copilot, every tools/call passes the same four gates before it touches your data.

01

Auth

sha256-hashed API key

02

Scope

8 fine-grained scopes

03

Tenant

isolation, enforced

04

Audit

every call logged

Scopes

stores:readmembers:readmembers:writecaptures:readcoupons:readcoupons:writepoints:write*

Two-way MCP

The same protocol, the other direction.

Inbound, Flash is an MCP server agents call. Outbound, Flash is an MCP client into external CDPs — pulling per-member data to personalize email at render time. The transport, circuit breaker, concurrency limiter, session pool, and token rotation are all hand-rolled with zero extra dependencies.

Circuit breaker

closed → open → half-open, rolling window

Concurrency limit

bounded promise queue

Session pool

least-pending SSE sessions + health checks

Token rotation

per-tenant, refreshed before expiry

Into email personalization

A registry of nine data-source adapters (merge tag, webhook, AWS Personalize, Recombee, Algolia, Bloomreach, Shopify, and the MCP CDP adapter) feeds the render pipeline per recipient. If a source fails, the recipient degrades to an empty result and the fallback chain takes over — no broken send.

CDPadapterper-recipient datapersonalized email
Early accessOutbound CDP gateway

The gateway is built and config-gated: without CDP credentials it simply stays disconnected and degrades per recipient. We don't present it as production-proven at scale.

Why it's different

Beyond REST and Zapier.

A REST API is a fixed, service-specific interface. Zapier is event-driven automation. MCP is the open standard agents discover and call on demand— and it's what the industry is consolidating around.

Typical approach

Traditional REST integration

Hard-wired endpoints an agent can't discover; you maintain the glue.

Flash, by design

Self-describing MCP tools agents find via tools/list and call on demand.

Typical approach

Zapier / iPaaS

Pre-built event triggers, not on-demand agent action.

Flash, by design

Agents invoke capabilities in the moment, under your scopes and audit.

Typical approach

Raw API tokens in a chat

All-or-nothing access, no boundary, no trail.

Flash, by design

Scoped keys, enforced tenant isolation, and a logged audit trail on every call.

AI & innovation

On the standard the whole industry is converging on.

MCP — introduced by Anthropic, donated to the Linux Foundation's Agentic AI Foundation, and now GA inside Microsoft Copilot Studio — is becoming the way business capabilities are exposed to AI agents with governance and audit. Flash was built MCP-native, both directions.

AI-discoverable capabilities

Agents find what Flash can do at runtime, instead of waiting for someone to hard-code an endpoint.

Governance built in

Identity, fine-grained scopes, tenant isolation, and audit — exactly the enterprise gap 2025's MCP work closed.

Zero-dependency client stack

Circuit breaking, concurrency, session pooling, and token rotation, all hand-rolled — fewer moving parts to trust.

What changes for the business

Your retention capabilities become safe, callable tools for the AI agents your team already uses.

14 tools

loyalty, members, coupons & more, agent-callable

8 scopes

fine-grained access, enforced per key

Two-way

inbound for agents, outbound into your CDP

Call your retention stack from your favorite agent.

We'll connect Flash to Claude, Cursor, or Copilot live — and show a governed tool call act on a member, under audit.