@pipeworx/eventbrite

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/eventbrite’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 2

Eventbrite event discovery by city/category, and single-event detail (venue, organizer, ticket price range).

Tools

• eventbrite_city_events(city, category?, keyword?, page?) — upcoming events in a city, optionally filtered by category slug (e.g. "music", "food-and-drink") and/or a free-text keyword. Returns event name, time, venue, category tags and a ticket URL. An unrecognized category slug is silently ignored by Eventbrite (falls back to all categories) rather than erroring, so the response carries category_applied to say whether the filter actually took.
• eventbrite_event(event_id) — full detail for one numeric Eventbrite event id: description, start/end time, venue, organizer, and ticket price range/availability.

Neither tool returns attendee or guest lists — Eventbrite does not expose those without authentication, and this pack would not surface them even if it could.

Auth

Keyless. Both surfaces are Eventbrite’s own public pages/endpoint with no login wall: a bad event id answers a clean 404 (“event does not exist”), and a bad city answers a clean 404 from the discovery page — neither reads as an auth failure.

Eventbrite retired its public v3 search API; it now answers 401 to a missing CSRF token/Referer, which this pack does not forge. Both tools here use surfaces that do not require that: the per-event detail endpoint, and the server-rendered city/category discovery pages a browser gets.

Data sources

• Eventbrite — event-discovery pages (city/category browse and keyword search) and single-event detail. Routes live only in src/index.ts.

Notes

• eventbrite_city_events accepts free-text city names (“San Francisco, CA”, “London”, “Austin, TX”) — Eventbrite’s own place lookup resolves them; an unresolvable city answers a clean 404 rather than a silent empty result.
• Results page at 20 events/page (Eventbrite’s own page size past page 1); page is 1-based.
• Eventbrite rate-limits these pages by IP. The pack does not retry on 429 — a caller should back off and retry later rather than hammer it.
• eventbrite_event’s price fields reflect ticket tiers as currently configured and can be 0.00 for a genuinely free event.

Tools

• eventbrite_city_events — Find upcoming Eventbrite events in a city, optionally filtered by category and/or keyword. Reads Eventbrite’s own public event-discovery pages (the same data a browser gets at eventbrite.com/d//
• eventbrite_event — Get full detail for one Eventbrite event by its numeric event id: description, start/end time, venue, organizer, and ticket price range/availability. Does not include attendee/guest lists.