The Model Context Protocol (MCP) integration lets compatible AI clients inspect and manage contests through a private, shop-scoped server URL.

MCP includes write tools. Connect only trusted clients and review sensitive actions—especially status changes and winner selection—before allowing them to run. Ongoing contests are configured and their draws confirmed in the contest editor.

## Enable MCP

1. Open **UserLoop Contests** in Shopify admin.
2. Go to **MCP**.
3. Turn on **Enable MCP**.
4. Copy the personal MCP server URL immediately. The full key is shown only when it is created.

The page provides one-click setup for Cursor and VS Code, a command for Claude Code, connector instructions for Claude and ChatGPT, and JSON for other Streamable HTTP clients.

## Read tools

| Tool | What it returns |
|---|---|
| `list_contests` | Contests with entry counts and performance data |
| `get_contest` | One contest with its prizes and actions |
| `get_contest_stats` | Entries, winners, views, and conversion rate |
| `get_entries` | Searchable, paginated entrant data |
| `get_winners` | Winners with entrant and prize details |
| `get_entries_over_time` | Daily entry counts for up to 365 days |

The time-series tool gives an AI client the data needed to summarize trends or draw a chart. The visual format depends on the client you use.

## Write tools

| Tool | What it changes |
|---|---|
| `create_contest` | Creates a contest with confirmed title and dates |
| `update_contest` | Changes supported fields, including customer-facing language |
| `update_contest_status` | Activates, deactivates, ends, or archives a contest |
| `add_prize` | Adds a product or custom prize |
| `select_random_winner` | Runs a weighted random draw for a prize |
| `select_manual_winner` | Awards a prize to a specified eligible entry |
| `select_most_voted_winner` | Awards an eligible highest-voted photo |
| `finish_contest_without_winner` | Resolves winner selection without awarding a prize |
| `reopen_winner_selection` | Reverses a no-winner decision |

For an ongoing contest, the MCP `update_contest` and `update_contest_status` tools do not change its end date. The one-off random, manual, most-voted, and no-winner tools cannot resolve its scheduled draws. Open **Results** under **Scheduled draws** to accept or redraw a proposed winner, or use **Run draw now**. See [Ongoing Contests](https://docs.contests.userloop.io/hc/userloop-contests/articles/contests-ongoing-contests).

## Example prompts

- “List my active contests and compare their conversion rates.”
- “Chart entries for this contest over the last 90 days.”
- “Create a French draft contest called Autumn Giveaway from 1 September to 30 September.”
- “Show the eligible entries and remaining prizes before drawing.”
- “Select the most-voted eligible photo for the grand prize.”

Ask the client to inspect a contest before changing it. MCP writes are applied to the connected store when invoked; they do not use Sidekick's inline confirmation card.

## Protect the URL

The personal URL contains an API key. Treat it like a password:

- Never paste it into a public ticket, document, screenshot, or repository.
- Add it only to trusted clients and workspaces.
- Use **Regenerate URL** if it is lost or exposed. This revokes the previous key.
- Disable MCP when it is no longer needed; connected clients immediately lose access.

If a client does not show a recently added tool, refresh or rescan the MCP server. Remove and reconnect it with a regenerated URL if its tool cache does not update.