Eventbrite MCP Server

If you already use Eventbrite, the eventbrite mcp server is the piece that lets your assistant work with it directly. Eventbrite MCP server providing event management and ticketing capabilities.

What the server does

An MCP (Model Context Protocol) server that provides comprehensive event management and ticketing capabilities through the Eventbrite API v3.

• Event Management — Create, update, publish, delete, cancel, and copy events
• Ticket Management — Create, update, and manage ticket classes
• Order Management — Retrieve and list orders
• Attendee Management — Get and list attendee information
• Organization Support — Manage organizations, venues, and members
• Discount Management — Create and manage discount codes

Installation

The server ships on npm as @prmichaelsen/eventbrite-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• EVENTBRITE_API_TOKEN — Your Eventbrite API token (required)
• create_event — The create_event tool exposed by this server
• update_event — Update an existing event by event ID. Supports partial updates
• create_ticket_class — The create_ticket_class tool exposed by this server
• publish_event — Publish an event to make it live and available for ticket sales
• Setup — The Setup tool exposed by this server
• Testing — The Testing tool exposed by this server
• Building — The Building tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: EVENTBRITE_API_TOKEN, EVENTBRITE_API_URL, PLATFORM_SERVICE_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Eventbrite's toolset — EVENTBRITE_API_TOKEN, create_event, update_event and 5 more — is a fair guide to whether it matches your workflow. It is maintained by prmichaelsen; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Eventbrite's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.