Sweeppea MCP

Sweeppea MCP: Professional US & Canada Sweepstakes Compliance Manage sweepstakes, participants, and winner drawings directly through a unified interface.

CommunityRequires local installNo sign-inGlobalFreeCan modify data
This server only runs on your computer. It cannot be added to Claude or ChatGPT web. See the project docs for installation.

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    Sweeppea MCP: Professional US & Canada Sweepstakes Compliance

    Manage sweepstakes, participants, and winner drawings directly through a unified interface. Create official rules, schedule events, and handle support tickets to streamline your promotion workflow while ensuring legal compliance across the United States and Canada.

    🚀 How It Works The Sweeppea MCP Server acts as a secure bridge between AI assistants and the official Sweeppea API. It translates natural language interactions into structured API calls, giving your AI assistant control over:

    Participant Management & Winner Drawings.

    Legally Compliant Official Rules Generation.

    Promotion Calendars & Event Scheduling.

    Real-time Billing & Data Insights.

    Architecture Flow Your AI Assistant → MCP (Protocol) → Sweeppea MCP Server → Sweeppea API v3

    🔐 Authentication & Pricing This MCP server requires a Sweeppea API Key tied to an active subscription.

    Why a Professional Service? Running sweepstakes in the United States and/or C

    Requires a local install: run the server on your machine, then point your client at it.

    How to connect

    How to connect Sweeppea MCP to Claude

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    How to connect Sweeppea MCP to ChatGPT

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    How to connect Sweeppea MCP to Cursor

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    This server runs locally: it is wired up through the client config, and the project documentation carries the steps.

    Tools not fetched yet: the server requires sign-in; the list appears after a manual check.