# eventbrite-mcp [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/chrischall/eventbrite-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 1660  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/eventbrite-mcp

## Description
Eventbrite for Claude — your tickets/orders, organizer data, and public event discovery

## Tools
Capabilities this server exposes over MCP:

- **eb_me** — Get the authenticated Eventbrite user's profile (id, name, primary email).
- **eb_my_orders** — List the authenticated user's ticket orders (attendee side), with the event expanded. time_filter narrows to upcoming or past events.
- **eb_my_organizations** — 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_events** — List an organization's events (as organizer), optionally filtered by status.
- **eb_org_attendees** — List attendees across an organization's events (organizer side).
- **eb_org_orders** — List orders across an organization's events (organizer side).
- **eb_org_venues** — List an organization's saved venues (name, address, geo).
- **eb_org_discounts** — List an organization's discount and access codes, including their usage limits.
- **eb_org_ticket_groups** — List an organization's ticket groups (ticket classes bundled across events).
- **eb_org_webhooks** — List an organization's registered webhooks and the actions they subscribe to.
- **eb_org_report** — Run an organization's sales or attendees report — the aggregated analytics behind its events, optionally windowed by date.
- **eb_event** — 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-<id>).
- **eb_ticket_classes** — List an event's ticket classes (name, cost, free/paid, on-sale status).
- **eb_event_description** — Get an event's full HTML description.
- **eb_reference** — 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_attendees** — 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_attendee** — Get one attendee of an event by id (barcode, profile answers, check-in state).
- **eb_event_orders** — List a single event's orders (organizer-side; requires access to that event).
- **eb_ticket_class** — Get one ticket class of an event by id. Use eb_ticket_classes to list them first.
- **eb_event_questions** — 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_order** — 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_venue** — Get a venue by id (name, address, geo). Venue ids appear on expanded events and in eb_org_venues.
- **eb_venue_events** — List the events held at a venue.
- **eb_organizer** — Get an organizer's public profile by id (name, description, logo, social links).
- **eb_organizer_events** — List an organizer's events — the public way to see everything one organizer is running.
- **eb_series_events** — List the occurrences of a recurring event series. Search results and events carry a series_id when they belong to one.
- **eb_user** — Get a public user profile by id. Use eb_me for the authenticated user (that call also returns private fields like emails).
- **eb_resolve_place** — 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_events** — 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_details** — 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_healthcheck** — 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'.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "eventbrite-mcp": {
    "command": "npx",
    "args": ["-y","@chrischall/eventbrite-mcp"],
    "env": {
      "EVENTBRITE_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `EVENTBRITE_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What eventbrite-mcp MCP server does

eventbrite-mcp MCP server exposes read-only Eventbrite data through MCP tools. It covers the authenticated user's profile and orders, organizer organizations, organizer events and venues, event attendees and orders, ticket classes, registration questions, venue and organizer records, recurring-series occurrences, public user profiles, and reference data such as categories, regions, countries, formats, and time zones.

The server also supports public event lookup and discovery. Agents can retrieve an event by ID, resolve a location into an Eventbrite place ID, search consumer event listings, request compact search results, use facets, and fetch details for multiple events. Organizer reporting provides date-windowed sales and attendee analytics.

## How it works

Two request paths are used. The documented Eventbrite API at `eventbriteapi.com/v3` handles token-based account, organizer, event, and reference requests. Set `EVENTBRITE_TOKEN` to a private OAuth token created through Eventbrite's API-key flow.

Consumer discovery uses Eventbrite's site API, which is not reachable reliably from a server-side client because of site-side blocking. Discovery requests instead pass through a fetchproxy-compatible ContextMint Bridge browser extension and an authenticated `eventbrite.com` tab. The browser session supplies the required signed-in context for search-related requests.

A typical discovery sequence resolves a location such as `Charlotte, NC`, then passes the returned place ID to `eb_search_events` along with a query such as `blues`. Bare cities without a state or country are rejected rather than inferred; raw location slugs are also accepted.

## Setup and configuration

Install the package globally with `npm install -g @chrischall/eventbrite-mcp`, then configure the executable as an MCP server. The documented Claude Code configuration uses the `eventbrite-mcp` command and supplies `EVENTBRITE_TOKEN` in its environment.

The token is optional at startup. Without it, account and token-backed tools report an error when used, while discovery tools can still operate through the browser bridge. To enable discovery, install ContextMint Bridge from its releases, load the Chrome extension unpacked, keep an Eventbrite tab open, and approve the one-time pairing prompt. The project notes that Safari support is planned inside a ContextMint app that does not yet have a public download.

## Tools and capabilities

- Inspect the current profile, personal orders, tickets, and expanded event information.
- Browse organizer events, venues, attendees, orders, and date-bounded reports.
- Read event ticket classes, attendees, orders, questions, venue details, and recurring-series events.
- Query public event, organizer, venue, and user records by identifier.
- Search consumer listings, resolve places, retrieve event facets, and batch event details.
- Poll event attendees incrementally with `changed_since` and check connection or credential status with `eb_healthcheck`.

## Limitations and notes

The eventbrite-mcp MCP server does not create, update, or delete Eventbrite data: every exposed tool is read-only. Eventbrite's consumer discovery path depends on a signed-in browser tab and the bridge, so discovery availability differs from token-backed API access. `eb_healthcheck` can distinguish missing credentials, rejected credentials, bridge or edge blocking, timeouts, HTTP failures, and transport failures. With neither a usable token nor a bridge, it reports the missing-credential condition.

_Full upstream README: https://allmcps.com/mcp/eventbrite-mcp/readme_