Skip to main content

How-to · 5 minutes

How to build an MCP agent that operates on Social Perks

Social Perks runs an MCP server at /api/mcp exposing five tools (getPricing, listActions, getBenchmarks, listCampaigns, searchInfluencers) over JSON-RPC 2.0. Any MCP-capable client (Claude Desktop, Cursor, Cline, etc.) can connect and operate on the platform. The full setup takes under five minutes.

Before you start

  • An MCP-capable client (Claude Desktop, Cursor, Cline, or a custom MCP client)
  • A Social Perks API key (mint at /dashboard/api-keys after signing in)

Steps

  1. Add the MCP server to your client config

    Add this to your MCP client's config file: { "mcpServers": { "social-perks": { "url": "https://socialperks.app/api/mcp", "transport": "http" } } }. Restart the client to pick up the change.

  2. Verify the tools list

    In your MCP client, ask 'what tools do you have for social-perks?'. The client should report: getPricing, listActions, getBenchmarks, listCampaigns, searchInfluencers. If it doesn't, check the URL and that the client supports the http transport.

    Open the relevant page →

  3. Try a no-auth tool first

    Ask the agent to call getPricing for actionId='ig_rl' (Instagram Reel). It should return the market value (~$4) and a recommended perk. No API key required for this — it's a public reference tool.

  4. Add your API key for authenticated tools

    For listCampaigns or any action that's scoped to your business, you need an API key. Mint one at /dashboard/api-keys after signing in. Set it in your client's environment as the x-api-key header on requests to /api/mcp.

    Open the relevant page →

  5. Use the AGENTS.md doc as the system prompt

    When configuring the agent's system prompt, include the relevant excerpts from /AGENTS.md so the agent knows what NOT to do (no fake submissions, no FTC-disclosure stripping, no key storage in chat output). The doc is written for exactly this use case.

    Open the relevant page →

Related guides