eventbrite

This MCP server provides natural language access to the Eventbrite API, enabling you to create, list, update, publish, and cancel events, as well as manage venues and browse categories. You can interact with the server through an MCP client by sending structured tool calls that map to the available actions (create_event, list_events, get_event, update_event, publish_event, cancel_event, list_categories, create_venue). Typical usage involves authenticating with your Eventbrite API key and (optionally) specifying your organization ID if you want to operate on org-specific data. After starting the server, you can issue natural-language requests via the MCP client and the server will translate them into Eventbrite API calls behind the scenes. The included tool descriptions show the required and optional parameters for each operation, guiding you to construct valid requests.

You can: create events with rich details including name, dates, description, venue information, and category; list and filter your events; retrieve details for a specific event; update event attributes; publish draft events; cancel events; list available categories; and create venues with name and address data. The environment variables must be configured with your Eventbrite API key, and you can optionally set the organization ID to scope actions to a specific organization. The client configuration example demonstrates how to expose the server to an MCP client with the proper environment variables.

Prerequisites:

• Node.js and npm installed on your system
• Access to the Eventbrite API with an API key

Step-by-step install:

1. Navigate to the project directory for the Eventbrite MCP server (as referenced in the README).
2. Install dependencies: npm install
3. Create or update your environment variables. At minimum, include:
   • EVENTBRITE_API_KEY (your Eventbrite API key)
   • EVENTBRITE_ORGANIZATION_ID (optional) You can place these in a .env file or export them in your shell.
4. Build the project (if you are working with TypeScript sources): npm run build
5. Run the server in development mode (with auto-reload if supported): npm run dev
6. Run the server in production mode: npm start
7. Connect an MCP client by configuring the mcpServers section with the appropriate command, path, and environment variables as shown in the usage example.

Tips and considerations:

• Ensure your EVENTBRITE_API_KEY is kept secret and never committed to source control.
• If you operate across multiple organizations, you may omit EVENTBRITE_ORGANIZATION_ID or provide it to scope operations.
• When deploying, consider using environment-specific .env files (e.g., .env.development, .env.production) to manage credentials.
• The index.js path in the MCP client configuration must point to the compiled/entry JavaScript for the server (adjust /path/to/cyber-guard/... as needed).
• If you encounter API errors, verify network access to Eventbrite endpoints and that the API key has the required permissions.
• The server supports creating and managing venues, which requires accurate address fields; provide country codes in ISO format where applicable.