Integration

Viral Loops integration

Viral Loops runs referral, waitlist and giveaway campaigns. Register participants, track their conversions, edit their names, counts and custom fields, look up a participant's data, rank, join order, referrer and referrals, query or search the campaign's participants, flag those who got early access or a reward so they leave the leaderboard, list pending and given rewards and redeem a pending one, and read the campaign's settings and lead and referral totals. Front-end widget and captcha fields and the public-token mode are not exposed. Authentication is the campaign's secret API token sent in the apiToken header; each token belongs to one campaign, so every call acts on that campaign.

Connect Viral Loops How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Viral Loops.Built from the 16 Viral Loops tools below, on the connection you add once.

What you can do with Viral Loops

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Participant, 6 operations

flag_participantsFlag participantsPOSTFlags participants who got early access or a reward: they leave the waitlist and leaderboard but stay in the campaign dashboard and exports. Returns status. Rate limit 300 requests per minute.
get_participantGet participantGETReturns one participant (by email or referralCode): name, referral code, rank, referral and points totals, referrer, custom fields, pending and redeemed rewards. Rate limit 300 requests per minute.
query_participantsQuery participantsPOSTReturns campaign participants in results, optionally only the listed participants or those referred by the listed referrers, paged with filter.limit and filter.skip. Rate limit 300 requests per minute.
register_participantRegister participantPOSTRegisters a new participant in the campaign (user.email required); pass referrer.referralCode to credit a referrer. Returns the participant's referralCode and isNew. Rate limit 80 requests per minute.
search_participantsSearch participantsPOSTSearches the campaign's participants by search term, conversion status (all, pending, converted) and source (referred, organic, all). Returns results, total, offset, limit. 300 requests per minute.
update_participantUpdate participantPUTEdits a participant found by email or referralCode: first name, last name, referral count, conversion count or custom fields. Leave a field out of newAttributes to keep it. Rate limit 300 requests per minute.

Reward, 3 operations

list_given_rewardsList given rewardsGETLists a participant's given (redeemed) rewards (by email or referralCode); leave both out to page through all participants and their given rewards. Rate limit 300 requests per minute.
list_pending_rewardsList pending rewardsGETLists a participant's pending rewards (by email or referralCode); leave both out to page through all participants and their pending rewards. Pass a reward id to redeem_reward. 300 requests per minute.
redeem_rewardRedeem rewardPOSTRedeems a pending reward (rewardId from list_pending_rewards) of a participant, moving it from pending to given rewards. Rate limit 300 requests per minute.

Campaign, 1 operation

get_campaignGet campaignGETReturns the campaign's public settings: name, company, template type, landing page, expiration, widget, popup and email settings. Rate limit 300 requests per minute.

Campaign stats, 1 operation

get_campaign_statsGet campaign statsGETReturns the campaign's total number of leads (participants) and its total referral count. Rate limit 300 requests per minute.

Conversion, 1 operation

convert_participantConvert participantPOSTRecords a conversion for a registered participant (user.email or user.referralCode), optionally with a value. Only for Milestone, Altruistic, Online to Offline, Universal Referral and Tempting Giveaway campaigns. 25 requests per minute.

Participant order, 1 operation

get_participant_orderGet participant orderGETReturns the order in which a participant (by email or referralCode) joined the campaign (1 for the first) and the campaign's lead count. Rate limit 300 requests per minute.

Participant rank, 1 operation

get_participant_rankGet participant rankGETReturns a participant's rank on the waitlist or leaderboard (by email or referralCode), with referral and points totals. Flagged participants are not ranked. Rate limit 300 requests per minute.

Referral, 1 operation

list_participant_referralsList participant referralsGETLists the referrals of a participant (by email or referralCode), paginated with limit and offset. The vendor documents no response fields. Rate limit 300 requests per minute.

Referrer, 1 operation

get_participant_referrerGet participant referrerGETReturns the referrer of a participant (by email or referralCode). The vendor documents no response fields. Rate limit 300 requests per minute.

Use Viral Loops from Claude Code, Cursor or Codex

Connect Viral Loops in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Viral Loops operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Viral Loops

Create your workspace
Sign up free. Nothing to install.
Connect Viral Loops once
Add your Viral Loops connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.