Sweeppea MCP Info MCP Server

Most payments and commerce work still happens through a UI a human drives. Sweeppea MCP Info MCP server moves it into the conversation instead. Official MCP server for sweepstakes management. 71 tools across 16 categories for legally compliant sweepstakes in the US and Canada.

The short version

The Sweeppea MCP Server is a secure bridge between AI assistants and the Sweeppea API. It translates natural language interactions into structured API calls, giving your AI assistant full access to sweepstakes management — participants, official rules, winners, calendars, billing, and more.

The tools it exposes

The server publishes 14 tools. What each one is for:

• health_check — Verify connection to Sweeppea API and validate your API key
• get_profile — Get user profile information for a Sweeppea account
• get_business — Get business information including company details and address
• get_plan — Get subscription plan details including pricing, limits and features
• get_entry_fields — Get all form fields for a sweepstakes entry page. Use before adding participants
• get_entry_settings — Get all entry page settings: display, colors, compliance, confirmation, winners, age gate, AMOE, and more
• update_entry_settings — Update 1-5 entry page settings per request. Supports 80+ configurable fields
• fetch_sweepstakes — Get all sweepstakes associated with your account
• create_sweepstakes — Create a new sweepstakes with type, handler, dates, and times
• update_sweepstakes — Update an existing sweepstakes (name, dates, times)
• clone_sweepstakes — Clone an existing sweepstakes with new parameters and dates
• pause_sweepstakes — Pause a sweepstakes, setting it to inactive while preserving data

What it needs from you

Configuration is passed through the environment: YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Sweeppea MCP Info's toolset — health_check, get_profile, get_business and 11 more — is a fair guide to whether it matches your workflow. It is maintained by sweeppea-development-lab; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Sweeppea MCP Info.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.