Developer Docs
MCP Server
Social Perks ships a Model Context Protocol server so AI agents can drive customer marketing the same way an admin would.
Endpoint
https://socialperks.app/api/mcp
Transport
streamable-http (stateless JSON-RPC)
Protocol
2025-03-26
Auth
Authorization: Bearer <key>
Anonymous
read-only tools only
Quick start — Claude Desktop
{
"mcpServers": {
"social-perks": {
"url": "https://socialperks.app/api/mcp",
"headers": {
"Authorization": "Bearer sp_live_your_key_here"
}
}
}
}Drop this in ~/Library/Application Support/Claude/claude_desktop_config.json, restart Claude, and the 10 tools below appear in any chat.
Tools
| Name | Auth | Description |
|---|---|---|
| getPricing | none | Market-rate pricing for a marketing action (USD value + recommended perk) |
| listActions | none | 125 marketing actions across 25 platforms |
| getBenchmarks | none | Industry benchmarks (engagement, conversion) by industry |
| listCampaigns | required | List campaigns owned by the API key's business |
| searchInfluencers | none | Search influencers by platform / follower count |
| createCampaign | required | Launch a new campaign for the API key's business |
| submitProof | required | Submit proof of completion for a campaign action |
| reviewSubmission | required | Approve or reject a pending submission |
| listSubmissions | required | List submissions (filterable by status, campaign) |
| getCampaignStats | required | Aggregate stats for a campaign — completions, conversion, spend |
Get an API key
Sign in, then go to /admin/api-keys and click Issue. The plaintext token is shown once.
Why MCP-native?
Small business owners are starting to delegate operations to AI assistants. The platforms those assistants use have to be addressable by agents directly — not just by humans clicking buttons.
Every admin workflow on Social Perks is reachable through these 10 tools. The same audit log records both human and agent actions. The same tenant boundaries apply.
Listed in
v1.0.0 · protocol 2025-03-26 · streamable-http