Skip to main content
The MCP server lets AI clients query and manage your rewards data in natural language. It exposes the same read/write operations as the REST API as callable tools. Endpoint: https://mcp.rewards.so

​
Connecting Claude

​
Claude.ai + Claude Code — simplest

Go to claude.ai → Customize → Connectors and click Add connector. Fill in:
FieldValue
NameRewards
URLhttps://mcp.rewards.so
Save. An OAuth popup will ask you to authorize your Rewards account. Once approved, the connector is available in all Claude.ai conversations. Claude Code bonus: if you’re signed into Claude Code with the same account, connectors you’ve added on claude.ai automatically appear in Claude Code — no extra setup needed.

​
Claude Code (CLI, alternative)

If you prefer to add it directly from the terminal: 
claude mcp add --transport http https://mcp.rewards.so
The OAuth flow opens in your browser. If the auto-redirect fails, copy the callback URL from your browser’s address bar and paste it back into the terminal.

​
Claude Desktop

Claude Desktop uses a separate config file — it does not sync with your claude.ai account. Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\Claude\claude_desktop_config.json on Windows: 
{
  "mcpServers": {
    "rewards": {
      "url": "https://mcp.rewards.so"
    }
  }
}
Restart Claude Desktop. A browser window will open to authorize access on first launch.
All clients support OAuth natively via RFC 7591 Dynamic Client Registration — no pre-configured credentials needed.

​
Connecting other clients (Cursor, etc.)

Clients that don’t support OAuth can authenticate with an API key. Generate one in Dashboard → Integration, then pass it as a Bearer token: 
{
  "rewards": {
    "url": "https://mcp.rewards.so",
    "headers": {
      "Authorization": "Bearer rw_yourkey"
    }
  }
}
Keys with read permission enable read-only tools; keys with all permission enable read and write tools. If your key has access to multiple point systems, add: 
X-Point-System-Id: <your-point-system-uuid>

​
Available tools

​
Read tools

ToolDescription
get_leaderboardTop wallets ranked by points. Params: limit (1–200), page
get_walletPoints, rank, events, and blacklist status for an address or ENS name
search_walletsSearch wallets by address substring. Params: query, limit
get_wallet_eventsFull point history for a wallet
get_blacklisted_walletsList of banned wallets with reasons
get_point_systemMetadata and stats (total wallets, total points, ban count)

​
Write tools

Write tools require an all API key or OAuth with write scope.
ToolDescription
add_pointsAdd points to a wallet (creates it if new). Params: address, amount, eventType (optional)
ban_walletBlacklist a wallet. Params: address, reason
unban_walletRemove a wallet from the blacklist. Params: address
All tools accept ENS names (.eth) in addition to 0x addresses.

​
Resources

The server also exposes two readable resources:
URIDescription
leaderboard://currentTop 100 wallets as plain text
wallet://{address}Wallet summary as plain text

​
Example prompts

"Analyse le top 50 du leaderboard et identifie les wallets qui semblent farmer"
"Ban tous les wallets avec moins de 3 events distincts et plus de 10 000 points"
"Montre-moi l'historique complet de 0x1234..."
"Ajoute 500 points à vitalik.eth pour l'event discord_launch"
"Quels wallets ont été bannis cette semaine ?"

​
Audit trail

Every add_points, ban_wallet, and unban_wallet call is recorded in the activity log with the API key or OAuth client ID. All MCP actions are fully auditable from the dashboard.