SweepsyRun your sweepstakes in your AI agent with Sweepsy
Point Claude Code, Codex, Cursor or any MCP client at Sweepsy. It reads your campaigns, builds new ones, designs the pop-up and reports on entries, from your editor.
Agent access starts when Sweepsy accepts your brand. See how to ask for it.
How to connect
One address works in every client that supports a remote MCP server.
Step 0 Get Sweepsy’s acceptance first
Agent access is by approval. Sign in, open your workspace page, and press Request agent access. A Sweepsy admin reviews your brand. Until Sweepsy accepts it, your agent’s sign-in ends on a page that says your brand is not accepted yet.
Copy the connector URL
This is the address of the Sweepsy server.
https://trysweepsy.com/api/mcpAdd it in Claude
Open Settings, then Connectors, and choose Add custom connector. Paste the address. Or let the button fill it in for you.
Add to ClaudeConnect, sign in and start
Your browser opens: sign in to Sweepsy and approve the request. Your agent never sees your password.
Connecting an agent needs a brand that Sweepsy has accepted. Nothing is stored in a config file: no API key, no secret. The connection uses OAuth 2.1 with PKCE, and the token it issues expires and refreshes on its own.
What your agent can do
Ask your agent in plain words. Start with “what Sweepsy brand am I connected to?” The server answers with your brand, your campaigns and exactly what this connection may change.
11 prompts
Plan a sweepstake
Point your coding agent at Sweepsy and it can read your campaigns, build new ones, design the storefront pop-up and badge, test what a basket earns, and report on entries and winners, without leaving your editor.
Plan a Black Friday sweepstake for my store: a draft campaign, the ticket rules and two prize tiers. Do not launch it.
Who am I connected to?
Start here. The server answers with your brand, your campaigns and exactly what this connection may change.
What Sweepsy brand am I connected to, and what may this connection change?
Check your campaign
Read the shared campaign your store takes part in: dates, prize, ticket rules and status.
Show me the shared campaign my store is in, its dates and how many entries it has so far.
Test the rules
Try a real basket and see which rules matched and how many tickets it earned, before a shopper ever meets it.
Try a $120 basket with two hoodies and tell me which rules matched and how many tickets it earned.
Design the pop-up and badge
Colours, image, icon, copy, and which products show no badge.
Give the pop-up our brand colours, use our logo as the icon, and show no badge on gift cards.
Build the storefront pop-up
Pick one of six templates, each with a countdown, then set the colours, words, image and timing.
Make our pop-up the ticket template in our brand colours, with the button going to /collections/all.
Place it
Get the embed script for your storefront, already carrying your public key, in floating, inline or tracking-only mode.
Give me the embed script for my custom storefront in inline mode.
Build your own
Read the same public payload the Sweepsy widget renders from and write a custom component against it.
Read the widget payload and build a React pop-up that keeps the rules link, the free entry link and the no-purchase sentence.
Check the launch
Run the real launch gate and read every blocker, as often as you like. Start the campaign once it passes and you have said so.
Check whether my spring campaign is ready to launch and list every blocker. Do not start it yet.
Track it
Entries, participants, tickets, revenue, a daily curve, the widget funnel, and whether one shopper’s entry counted.
How many entries, participants and tickets did my campaign get this week, and how does the widget funnel look?
Read the draw
Draw records, winners and a one-command verification that the published result replays from the published seed.
Show the draw record and the winners of my last campaign, and check that the result replays from the published seed.
What it will not do
Three refusals are built in, and they are not settings. They are the reason the consent screen can be short.
It cannot publish or change your official rules.
The rules are a legal instrument. Entries are recorded against the exact version in force, a published version never changes, and a named person approves the text.
It cannot run a draw or touch a winner.
One administrator seals the draw and a different one executes it, against a frozen ticket list, under the committee your rules name. Notifying a winner and confirming a claim are the same kind of act.
It cannot read your entrants.
Names, phone numbers, postal addresses and full email addresses are never returned. Entry listings show a masked address. There is no tool that exports a participant list.
Two more limits follow from the product rather than the law. Ticket rules, prizes and dates freeze once a campaign leaves draft, because shoppers entered under them. Starting or closing a campaign needs an explicit confirmation, because both change what the public sees.
What it is
Sweepsy speaks the Model Context Protocol: an open standard that lets an AI agent call a service directly instead of guessing at an API. The Sweepsy server is hosted, so there is nothing to install and nothing to keep updated.
Sweepsy must accept your brand first. Open Request agent access in your workspace at trysweepsy.com/app/mcp, and a Sweepsy admin reviews it. Until your brand is accepted, the agent’s sign-in ends on a page that says your brand is not accepted yet.
Once your brand is accepted, you sign in with your normal Sweepsy account and approve the agent on a consent screen. The access it receives is bound to one brand (yours) and to the two things you agreed to.
Building a custom pop-up
If the hosted widget is not the design you want, your agent can read the public payload and build the component itself. Ask for it and the server hands over the widget contract first.
One rule survives every redesign. Any surface you build must show, within one tap of the offer: a link to the official rules, a link to the free entry route, and the no-purchase sentence the payload returns. Those three are what separate a lawful prize promotion from an unlawful lottery in most territories, and the wording is approved as it stands.
Fetch the payload at runtime rather than baking it into the page. Prizes, close dates and ticket rates change, and a stale one is a false statement to a shopper.
Disconnecting
Open Company in your Sweepsy workspace. Every connected agent is listed with when you connected it and when it last called. Disconnect ends its access on the next request. There is no cached decision to wait out.
Every change an agent makes is written to your audit log under your name, with the agent that made it recorded beside it.
Questions, or something the server should do and does not? Contact our team.