eventbrite-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVENTBRITE_TOKEN | No | Your 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| eb_meA | 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_attendeesA | List attendees across an organization's events (organizer side). |
| eb_org_ordersA | List orders across an organization's events (organizer side). |
| eb_org_venuesA | 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_classesA | 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_eventsB | List the events held at a venue. |
| eb_organizerA | Get an organizer's public profile by id (name, description, logo, social links). |
| eb_organizer_eventsB | 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 |
| 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 | Round-trips a small public www.eventbrite.com URL (/api/v3/categories/) through the fetchproxy bridge and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'real www.eventbrite.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 31 tools
Most tools have a clear resource-and-scope target (venue, order, attendee, ticket class), and the descriptions are careful about organizer vs attendee vs public views. The main risk is eb_event vs eb_event_details and the multiple order/attendee list variants, which could cause misselection if an agent skims names.
The eb_ prefix is used everywhere, and singular nouns (eb_event, eb_order) vs plural nouns (eb_event_attendees, eb_org_orders) reliably distinguish single-get from list operations. A few one-offs like eb_resolve_place, eb_search_events, eb_healthcheck, and eb_event_details break the pure resource-noun pattern but remain readable.
At 31 tools this surface is heavy; it exceeds the 25-tool threshold and will consume meaningful agent context. The breadth is defensible for Eventbrite's read domain, but several list/get variants could likely be consolidated.
Read coverage is extensive: events, venues, organizers, orders, attendees, ticket classes, questions, discounts, webhooks, reports, and public search are all represented. However, there are no create/update/delete operations, no attendee check-in mutations, and no webhook registration, which are notable gaps for a full Eventbrite lifecycle.