Eventbrite MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVENTBRITE_API_KEY | Yes | Your Eventbrite API key | |
| EVENTBRITE_ORGANIZATION_ID | No | Your Eventbrite organization ID (optional) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_eventC | Create a new event on Eventbrite |
| list_eventsB | List events for the authenticated user or organization |
| get_eventB | Get details of a specific event |
| update_eventC | Update an existing event |
| publish_eventA | Publish a draft event to make it live |
| cancel_eventC | Cancel an event |
| delete_eventA | Delete an event (permanently removes the event) |
| delete_canceled_eventsB | Delete all events that are marked as canceled |
| list_categoriesA | List available event categories |
| create_venueB | Create a new venue |
| create_webhookC | Create a webhook for Eventbrite events |
| list_webhooksB | List all webhooks for the organization |
| delete_webhookB | Delete a webhook |
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 13 tools
Tools are mostly distinct, with clear purposes. Minor overlap exists between cancel_event (changes status to canceled) and delete_event (permanent removal), and delete_canceled_events is a bulk operation. Overall, an agent can differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_event, create_event, list_events). Verbs are uniform and predictable, making it easy to infer tool function.
13 tools is appropriate for an event management server, covering core event operations (CRUD, status changes), categories, venues, and webhooks. The scope is well-defined without unnecessary bloat.
Event CRUD and status management are complete, but venue tools lack update/delete, webhooks lack update, and there are no tools for tickets, orders, or attendees. These gaps may hinder complex workflows.