MCP server for AI agents

Connect

The server speaks MCP over streamable HTTP: JSON-RPC 2.0 POSTs to one URL, answered with JSON, no session to keep. It authenticates with a key in the Authorization header, so your client must be able to send a header. Create the key first: a brand owner in the console (Integration tab, API keys), a partner in the portal (Your API keys). What each key and role can do.

claude mcp add --transport http viralpayouts https://viralpayouts.com/api/mcp \
  --header "Authorization: Bearer vpk_..."

{
  "mcpServers": {
    "viralpayouts": {
      "url": "https://viralpayouts.com/api/mcp",
      "headers": { "Authorization": "Bearer ${env:VIRALPAYOUTS_KEY}" }
    }
  }
}

{
  "mcpServers": {
    "viralpayouts": {
      "command": "npx",
      "args": ["mcp-remote", "https://viralpayouts.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer vpk_..." }
    }
  }
}

Apps that connect with a sign-in (Claude custom connectors, ChatGPT and other OAuth clients) need no key: see Connect from Claude or ChatGPT.

Agents can find the server at /.well-known/mcp.json, which also points to the OpenAPI document.

Connect from Claude or ChatGPT (sign in, no key)

Claude, ChatGPT and other MCP clients that connect with a sign-in can use this server without an API key. Give the app the server URL https://viralpayouts.com/api/mcp. The app registers itself, sends you to ViralPayouts to sign in and approve, and gets its own access, which you can disconnect at any time. Nothing has to be set up on the ViralPayouts side first.

What the consent page shows: the app's name, the website it will send you back to, and the accounts you can give it. A brand member chooses one brand and a role no higher than their own (viewer, manager or owner); a partner chooses read or write. The app then has exactly the tools an API key with that role or scope has. It can never change a payout account or tax form, and it stops working if you leave the brand's team.

Disconnect an app in the brand console (Integration tab, Connected apps) or in the partner portal (Connected apps). In Claude Code: claude mcp add --transport http viralpayouts https://viralpayouts.com/api/mcp, then run /mcp to sign in.

How the tools behave

curl https://viralpayouts.com/api/mcp \
  -H "Authorization: Bearer vpk_..." -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_programs","arguments":{}}}'

Tools for a brand key (43)

The first 13 are the original agent tools. The rest each match one REST endpoint. “Needs” is the least role the key must have.

Tools for a partner key (21)

A partner key sees only these. “Needs” is the key's scope: read, or write for tools that change something.