Eventbrite

Eventbrite

This connector works with the events of one Eventbrite account through the Eventbrite API v3 (https://www.eventbriteapi.com/v3) with a private token: organizations, events, the event description, ticket types, attendees, orders, venues, discount codes and sales reports. It can create and update events, tickets and venues and publish or unpublish events after you confirm.

Setup (about 2 minutes)

1. Sign in to Eventbrite and open https://www.eventbrite.com/platform/api-keys (Account settings, Developer links, API keys). If there is no key yet, click Create API key and fill in the short form.
2. Copy the Private token (not the API key, client secret or public token) into EVENTBRITE_PRIVATE_TOKEN and install. It is sent as Authorization: Bearer <token> to www.eventbriteapi.com only.
3. Check the setup with eventbrite_get_current_user, then eventbrite_list_my_organizations.

The token acts as the Eventbrite user who created it, with all of their organizations: share the MCP server only with people allowed to see attendees and orders.

How to work

1. Start with eventbrite_list_my_organizations: almost every tool needs an organization_id (not the organizer id from a profile URL).
2. Events: eventbrite_list_events (default upcoming events; time_filter past or all for older ones), eventbrite_get_event, eventbrite_get_event_description.
3. Sales and guests: eventbrite_list_ticket_classes, eventbrite_list_attendees (with check-in state), eventbrite_get_attendee, eventbrite_list_event_orders, eventbrite_list_organization_orders, eventbrite_get_order, eventbrite_get_sales_report and eventbrite_list_discounts.
4. Building an event, each step only after the user confirms: eventbrite_create_venue (or pick one with eventbrite_list_venues), eventbrite_create_event (a draft), eventbrite_create_ticket_class, eventbrite_set_event_description, then eventbrite_publish_event to go live. Change things later with eventbrite_update_event and eventbrite_update_ticket_class; eventbrite_unpublish_event takes an event offline while it has no orders.
5. eventbrite_cancel_event and eventbrite_delete_event are installed switched off; an administrator turns them on deliberately. Both only work while an event has no orders.

Dates: send times in UTC as YYYY-MM-DDTHH:MM:SSZ (no milliseconds) together with the event timezone (Europe/Berlin). Answers carry start.local, start.utc and start.timezone.

Prices: ticket costs are CURRENCY,amount in the smallest unit: EUR,2500 is 25.00 EUR. Answers show amounts as objects with display (e.g. "€25.00").

Paging: list answers have pagination.has_more_items and pagination.continuation; pass continuation for the next page.

No public search: Eventbrite removed public event search from the API in 2019, so this connector only sees events of the user's own organizations.

Common errors

• 401 INVALID_AUTH: the token is wrong or revoked, or the API key was pasted instead of the private token.
• 403 NOT_AUTHORIZED: the user has no permission for this organization or event.
• 400 ARGUMENTS_ERROR and similar: a field is invalid; error_description names it (e.g. DATE_CONFLICT, VENUE_AND_ONLINE, CANNOT_UNPUBLISH, PAGE_VERSION_DISCONTINUITY).
• 404 NOT_FOUND: no such event, order or organization for this user.
• 429 HIT_RATE_LIMIT: 2,000 calls per hour per token; wait and retry.

Out of scope here: refunds, check-in through the API, inventory tiers and reserved seating, ticket groups, custom questions, webhooks, media upload, series schedules and copying events.