MCP Connector

The Ploints MCP connector lets AI agents (Claude Desktop, Cursor, custom agents) interact with your loyalty program through natural language. It complements the REST API, SDK, Shopify app, and webhooks — it does not replace them.

What you can do

  • Check customer balances and tiers
  • Award or redeem points with idempotency protection
  • Create customers and fire custom events
  • List rewards, badges, and webhooks
  • Register webhooks (Growth+)
  • Issue badges (Pro+)

Requirements

Same as the REST API: Starter plan or higher for MCP access. Tier-gated tools (webhooks, badges, conversions) follow your subscription limits.

Option A — Local (npx)

Best for developers building integrations in Cursor or Claude Desktop.

# Run directly
PLOINTS_API_KEY=pk_your_key npx @ploints/mcp

# Claude Desktop / Cursor config
{
  "mcpServers": {
    "ploints": {
      "command": "npx",
      "args": ["-y", "@ploints/mcp"],
      "env": {
        "PLOINTS_API_KEY": "pk_your_key"
      }
    }
  }
}

Option B — Hosted remote

Best for business owners using cloud AI assistants. Copy the config from Dashboard → Integrations → AI Agent (MCP Connector).

{
  "mcpServers": {
    "ploints": {
      "url": "https://www.ploints.space/api/mcp",
      "headers": {
        "Authorization": "Bearer pk_your_key"
      }
    }
  }
}

Available tools

ToolPlanDescription
get_customer_balanceStarter+Balance, tier, XP progress
award_pointsStarter+Award points (requires idempotencyKey)
redeem_pointsStarter+Redeem points (requires idempotencyKey)
create_customerStarter+Enroll a new customer
list_rewardsStarter+Active reward catalog
register_webhookGrowth+Register outbound webhook
issue_badgePro+Issue a badge to a customer

Safety guardrails

  • All write operations require an idempotencyKey (min 8 characters) to prevent duplicate AI actions
  • Point awards and redemptions are capped at 10,000 per MCP operation
  • Use dryRun: true on award/redeem to validate without executing
  • Production flows (Shopify, POS) should continue using the REST API directly

Related docs