The Reggiee MCP API: Build Event Pages with AI Assistants

The Model Context Protocol (MCP) is an open standard that lets AI assistants like Cursor and Claude Desktop talk directly to external tools — your databases, APIs, and services — through a structured protocol.

We've built a full Reggiee MCP server so you can manage your entire event presence from inside your AI client. Create landing pages, wire up Klaviyo lists, configure Meta CAPI, and pull performance reports — all without opening a browser.

What you can do

The Reggiee MCP server exposes a complete set of tools:

Pages & Events

list_pages — see all your events and tours at a glance
create_event — spin up a new event page with title, dates, venue, images, and pixels in one shot
create_events_bulk — create an entire slate of events in one message
update_page — update any field: customisation, integrations, collect fields, consent, webhook, lineup, embeds
publish_page / unpublish_page — go live or take down a page instantly
delete_page — remove a page permanently

Tours

create_tour — describe the tour and its stops; the tool creates each stop event page first, then builds the tour linking them all
update_tour — add or remove stops, update tour details
delete_tour — delete the tour and optionally all its stops

Integrations

list_integrations — see which CRMs are connected
list_integration_lists — fetch all audience lists from Klaviyo, Mailchimp, or Brevo
create_klaviyo_list / create_brevo_list — create a new list directly from the conversation
assign_list_to_page — connect a list to an event so registrations sync automatically
suggest_list_for_page — get a best-match list recommendation for a page

Pixels

get_pixels — see workspace and page-level pixel configuration
add_pixel — add Meta, TikTok, Snapchat, or Google pixels to a page or workspace defaults
connect_meta_capi — configure your Facebook pixel ID and CAPI token in one step
remove_pixel — remove a pixel by ID

Reports

get_performance_report — registration counts, daily breakdown, top countries and referrers
configure_daily_report — set up or update scheduled report emails (daily/weekly/monthly, any timezone, optional Slack, AI summary)
get_report_settings — read current report settings for a page
list_page_reports — see all pages with reports configured
disable_report — pause reports without losing settings

Getting started

1. Upgrade to Pro

MCP API access is available on the Pro plan. Head to Settings → Billing if you haven't upgraded yet.

2. Generate an API key

Go to Settings → API Keys, enter a label (e.g. Cursor), and click Generate key. Copy the key — it starts with rmcp_ and is shown only once.

3. Add the MCP server to your AI client

Cursor — add to your .cursor/mcp.json:

{
  "mcpServers": {
    "reggiee": {
      "url": "https://reggiee-mcp.elabsagency.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer rmcp_YOUR_KEY_HERE"
      }
    }
  }
}

Claude Desktop — add to your claude_desktop_config.json:

{
  "mcpServers": {
    "reggiee": {
      "url": "https://reggiee-mcp.elabsagency.workers.dev/mcp?token=rmcp_YOUR_KEY_HERE"
    }
  }
}

4. Start building

Once connected, your AI client will list all available tools. Try:

"List my events and show me which ones have Klaviyo connected"

"Create an event called Summer Sessions at Fabric on 15th August 2026, starting at 10pm, collect email and phone, dark theme"

"Create a 5-city UK tour — London, Manchester, Birmingham, Leeds, Glasgow — starting September, each Friday night"

"Add my Meta pixel 1234567890 with CAPI token to my Summer Sessions event"

"Set up a daily report for Summer Sessions emailed to team@mycompany.com at 9am London time"

Security

API keys are stored as SHA-256 hashes — the plaintext is never saved after generation
Keys are scoped to your workspace only — MCP tools can only read and write your own data
Revoke any key instantly from Settings → API Keys
The MCP server validates that your workspace is on the Pro plan on every request

Ready to go? Generate your first API key →