Skip to main content
Glama
chrischall

eventbrite-mcp

by chrischall

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EVENTBRITE_TOKENNoYour personal Eventbrite OAuth token (free to create at https://www.eventbrite.com/platform/api-keys). Without it, the server still boots but account/organizer tools will error on first use.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
eb_meB

Get the authenticated Eventbrite user's profile (id, name, primary email).

eb_my_ordersA

List the authenticated user's ticket orders (attendee side), with the event expanded. time_filter narrows to upcoming or past events.

eb_my_organizationsA

List the organizations the authenticated user belongs to (organizer side). Use the returned org id with eb_org_events / eb_org_attendees / eb_org_orders.

eb_org_eventsB

List an organization's events (as organizer), optionally filtered by status.

eb_org_attendeesB

List attendees across an organization's events (organizer side).

eb_org_ordersA

List orders across an organization's events (organizer side).

eb_org_venuesB

List an organization's saved venues (name, address, geo).

eb_org_discountsA

List an organization's discount and access codes, including their usage limits.

eb_org_ticket_groupsB

List an organization's ticket groups (ticket classes bundled across events).

eb_org_webhooksB

List an organization's registered webhooks and the actions they subscribe to.

eb_org_reportB

Run an organization's sales or attendees report — the aggregated analytics behind its events, optionally windowed by date.

eb_eventA

Get an Eventbrite event by id (works for any public event, not just yours). Event ids are the trailing digits in an event URL (…-tickets-).

eb_ticket_classesB

List an event's ticket classes (name, cost, free/paid, on-sale status).

eb_event_descriptionB

Get an event's full HTML description.

eb_referenceA

List Eventbrite reference data: categories (103=Music, 101=Business, 110=Food & Drink, …), subcategories, formats, timezones, countries or regions. Category/subcategory/format ids feed eb_search_events filters.

eb_event_attendeesA

List a single event's attendees (organizer-side; requires access to that event). Use changed_since to poll incrementally instead of re-reading the whole list.

eb_event_attendeeA

Get one attendee of an event by id (barcode, profile answers, check-in state).

eb_event_ordersA

List a single event's orders (organizer-side; requires access to that event).

eb_ticket_classA

Get one ticket class of an event by id. Use eb_ticket_classes to list them first.

eb_event_questionsA

List the registration questions an event asks its buyers. Set canned=true for Eventbrite's standard question bank instead of the event's custom ones.

eb_orderA

Get a single order by id (the buyer-side record behind a ticket). Order ids appear in eb_my_orders / eb_event_orders results.

eb_venueA

Get a venue by id (name, address, geo). Venue ids appear on expanded events and in eb_org_venues.

eb_venue_eventsC

List the events held at a venue.

eb_organizerB

Get an organizer's public profile by id (name, description, logo, social links).

eb_organizer_eventsA

List an organizer's events — the public way to see everything one organizer is running.

eb_series_eventsA

List the occurrences of a recurring event series. Search results and events carry a series_id when they belong to one.

eb_userA

Get a public user profile by id. Use eb_me for the authenticated user (that call also returns private fields like emails).

eb_resolve_placeA

Resolve a location to Eventbrite's internal place id for eb_search_events. Accepts a plain location ('Charlotte, NC', 'Berlin, Germany') or a browse slug ('nc--charlotte'). A city on its own is rejected — include the state or country. Returns {placeId, name, slug, region, country} plus shelves — curated browse shelves (Popular, This Weekend, Online) harvested free from the same fetch.

eb_search_eventsA

Search public Eventbrite events (the consumer search absent from the documented API). Resolve the location to a place id first with eb_resolve_place. Filters: keyword, dates, category/subcategory/format ids (see eb_reference), free/paid, online-only. Answers with the slim per-event projection by default; pass view:"full" for Eventbrite's whole search envelope.

eb_event_detailsA

Batch-fetch public event details by id. Uses your bearer token by default, falling back to the browser bridge when no token is configured. For ticket-class detail prefer eb_ticket_classes.

eb_healthcheckA

Reports which hop is broken when a real tool fails. With EVENTBRITE_TOKEN set: Resolves the credential the way real tools do, then makes one authenticated request to www.eventbriteapi.com. Reports which source supplied the credential, whether www.eventbriteapi.com accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a www.eventbriteapi.com-side problem'. Read-only; never returns the credential itself. Without a token, discovery falls back to your signed-in browser tab, so it round-trips /api/v3/categories/ on www.eventbrite.com through that bridge instead and says the token is missing. Every failure carries an error.kind — e.g. 'credential_rejected', 'edge_blocked' (a CDN/WAF refused the request; the token was never judged), 'no_credential', 'timeout', 'http', 'transport'.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 31 tools

Disambiguation4/5

Most tools target distinct resources or scopes, and descriptions clarify attendee/order/event variants. However, eb_event and eb_event_details overlap on event retrieval, and eb_org_events/eb_organizer_events plus several org-vs-event attendee/order tools can be confused without careful reading.

Naming Consistency5/5

All tools use a consistent eb_ prefix and snake_case resource-oriented naming. There is no mixed casing or inconsistent verb style across the set.

Tool Count2/5

31 tools is well above the recommended 3-15 range and exceeds the 25-tool threshold for being too many. Many read variants could likely be consolidated without losing core capability.

Completeness3/5

The surface has broad read coverage across events, venues, orders, attendees, organizations, search, and reference data. However, it lacks create/update/delete or other write lifecycle operations, which are notable gaps for Eventbrite management workflows.

Maintenance

ActivityActive
ResponsivenessUnresponsive