Listing and reading events is enough to answer scheduling and attendance questions, and the included viewer means you can verify your token independently of the MCP path. Everything on the attendee and analytics side is still a checkbox in the plan, so treat this as read-only event lookup rather than event management.
An early MCP server over the Eventbrite API. Two tools are implemented today — listing events and reading one event's details — with attendee management and sales reporting marked as planned rather than shipped. The README is honest about that split, and it is the right thing to check before adopting it.
- `list_events` — list events with optional filtering, including by date range and by status
- `get_event_details` — the full record for one event
- A test client and a browser-based events viewer in the repository, so you can confirm retrieval works with your token before wiring the server into a client
An Eventbrite private API token from Account Settings → Developer Links → API Keys, supplied as `EVENTBRITE_API_KEY`. Node.js v18 or higher; `npm install` and `npm run build` from a clone, then point the client at `dist/index.js` with `cwd` set to the project directory. It speaks stdio.
Build from source — clone the repository and build it, then point your client at the binary