12 Things You Can Do With the Gleam MCP Server
Connect Claude or Codex to Gleam to draw winners, audit live campaigns, and swap prizes from one chat. 12 use cases with the prompts to copy.
• Draw winners for every Competition that ended overnight
• Pick one winner a week from that week's entries
• Audit every live campaign with one question
• Swap a prize straight from a Shopify product page
• Summarise a quarter's campaigns without opening the list
You've got six giveaways ending this month, and every one needs a winner drawn, a prize assigned and a check that nothing's broken before it closes.
The Gleam MCP Server connects an AI app like Claude or Codex to your Gleam site, so you can ask for that in one sentence. It reads your Competitions, Rewards and Captures. It can change the names, dates, prizes and images on Competitions and Rewards, and draw winners when you ask.
Setup takes a couple of minutes. Go to Settings > MCP on your site, click Create MCP Token, and follow the steps Gleam shows for Claude Code, Codex or the Claude app. It works on the Hobby Plan and above.
It can't create or delete campaigns, export entries or entrant details, edit the Actions inside a campaign or turn on the winner announcement.
A giveaway that ends at midnight on Friday leaves you drawing winners first thing Monday, or logging in over the weekend.
Claude's scheduled tasks run a prompt on a timer in the cloud, so the draw happens with your laptop shut. They're on the Pro, Max, Team and Enterprise plans. Add Gleam as a connector on claude.ai (scheduled tasks can't see one added with claude mcp add), then create a daily task for 7:07am and give it this prompt:
Find every Competition that ended in the last 24 hours with no winner drawn. Draw the winners and assign the prizes.
Gleam runs each draw in the background, and it usually finishes within a minute. The task then lists the campaigns it drew, each with a link to its Winners tab. Announcing the winner on the widget stays a one-click job for you.
Promised a draw at a set time, like 8pm on the night the giveaway closes? Make it a one-time task instead, set for 8:02pm so the last entries are in:
Draw one winner for the Spring Giveaway and assign the prize.
Runs set exactly on the hour can start several minutes late, which is why this one is set for 8:02pm.
Click Run now once before you leave a daily task running, so you can watch the first draw go through. If you'd rather check before every draw, have the task post the list of ended campaigns to Slack without drawing. Then tell Claude to draw once you've looked.
Keeping a long giveaway busy usually means building a new campaign every week.
Gleam can draw winners from a date range, so each Monday's draw only looks at last week's entries.
Draw one winner for the Summer Giveaway from entries made between Monday 2 and Sunday 8 November. Don't allow anyone who's already won.
Make it a weekly scheduled task for Monday morning and ask for "last Monday to Sunday" instead of fixed dates, so it works out the week itself. That's one campaign, one landing page and one set of Actions for the whole quarter, with a fresh winner to announce every week. Date range draws need a Business Plan or above.
You only find the missing prize image or last year's terms when an entrant points it out.
Which of my live Competitions have no prize image, end in the next 7 days, or use custom terms that mention 2025?
You get a list back with the reason for each one. Fix the image and the dates in the same chat. The connector can't rewrite custom terms, so Claude lists the campaigns to fix in the editor.
Run the same question as a daily scheduled task with the Slack connector added, and the list lands in your team channel every morning.
When bots hit, you're opening every live campaign one by one to turn the protection up. Do them all at once instead.
Set fraud protection to high on every live Competition and turn on email verification.
The higher fraud levels add CAPTCHA, login verification and protection against VPNs and data centres. Email verification can go on in the same sentence, and so can phone verification once a Twilio integration is connected to your site. Our guide to stopping bot entries covers the rest.
Every new prize means copying the name, price and image across from your store by hand. Paste the product link instead.
Make this the prize on the Spring Giveaway: https://embercoffee.co/products/home-brew-kit
Claude reads your product page and copies the image into Gleam (campaign images have to live in Gleam's storage). Then it updates the prize name, value and image. Images can be a jpg, png or gif of up to 2 MB, so a very large product shot may need a smaller version.
Halfway through a long giveaway, you've run out of things to post about it. A couple of runner-up prizes gives you something new to say.
Add two runner-up prizes to Win a Year of Coffee: an AUD $50 Ember voucher, then a bag of house blend.
Claude adds them under the main prize, in that order. When you draw for all prizes, Gleam gives the first prize to the first winner drawn and works down the list. If the campaign uses custom terms, update them in the editor to list the new prizes.
When a giveaway takes off, you're changing end dates campaign by campaign.
Push the end date of every live Competition with more than 5,000 entries back by a week.
Claude checks the entry count on each of your live campaigns, then moves the end date on the ones over your number. Check that the new date still suits your prize and your terms before you confirm.
Fixing rushed copy means opening every campaign and editing them one at a time. Pull every live title and description instead, rewrite them in your brand voice and review the changes before anything is saved.
Show me the title and description of every live Competition. Rewrite them in a friendlier tone, keep the prize details exact, and show me before and after for each one.
Gleam saves an update as soon as it runs, so tell Claude to wait for your go-ahead. You can approve some and leave the rest.
Reskinning every Reward for Black Friday eats an afternoon, and putting it back eats another. Change the names and images on every live Reward and Competition prize in one go, then put them back on 1 December. Two one-time scheduled tasks handle the timing: one on Thursday 26 November that makes the swap, and one on 1 December that reverses it.
Post the current name and image of every live Reward and Competition prize to #giveaways in Slack. Then swap each image for the matching Black Friday version from these links and add 'Black Friday' to each name.
The new images need to be online, in a shared folder or on your store's CDN. Gleam copies each one into its own storage.
The 1 December task reads that Slack post, so the change back is exact. For prize and Action ideas to go with it, see our Black Friday giveaway ideas. Capture popups can't be edited through the connector, so you'll still need the editor for those.
Checking which client giveaways need a winner means ten logins and ten campaign lists. Each MCP token works on one site, so if you're an agency, add a connector for each client site and give each one the client's name.
Which client Competitions end this week and still need a winner drawn?
You get one answer across every client, grouped by site, without logging in and out of each account.
Gleam for agencies covers team access and client sites in more detail.
After every draw, you're the one telling the team, logging it and checking the traffic. Claude can use other MCP servers in the same chat, so the draw can set off the rest of your routine:
- Post the campaign and prize to a Slack channel when a winner's drawn
- Log the giveaway's dates, prize and entry count in Notion
- Check GA4 for traffic to the campaign's landing page
The connector doesn't hand over entrant details, so the Slack post names the campaign and the prize, and you contact the winner from the Winners tab.
Finding the giveaways you never announced means clicking through every page of the campaign list, 25 campaigns at a time. Ask for the summary instead.
Summarise every Competition I ran last quarter: dates, prize, whether a winner was drawn and whether it was announced.
Claude reads each campaign and gives you one table. In the dashboard, Gleam shows an ended campaign in red until a winner is drawn and in blue until the winner is announced. The table puts every red and blue campaign from the quarter in one place, however many pages they're spread across.
Create a token in Settings > MCP and start with the audit prompt, which only reads your campaigns.
The number of winners you can draw depends on your Competitions plan and billing cycle. Expand this FAQ to see plan limits, how to configure winners, and how prize structure affects results.
Use Gleam’s built-in winner picker tool daily. Click to learn how to select a new winner and manage daily draws properly.
You can review your winners before finalising the draw. Winners will not be able to see that they've won unless you contact them, or announce them in your widget.
