You run an MCP server that bridges Eventbrite data with Model Context Protocol clients, enabling AI-assisted event management, attendee tracking, and analytics. This server authenticates with Eventbrite and exposes tools you can invoke from MCP clients to list events, view details, manage attendees, and generate reports.

How to use

You interact with the Eventbrite MCP Server through an MCP client. Start by configuring your client to connect to the local or remote MCP endpoint, then invoke tools to fetch events, attendee information, and analytics. The server handles authentication with Eventbrite using your API key and returns structured results you can feed into AI prompts, dashboards, or automation workflows.

How to install

# Prerequisites
# - Node.js v18 or higher
# - Eventbrite API token
# - MCP client (e.g., Claude Desktop)

# Install dependencies
npm install

# Build the project (if a build step is provided)
npm run build

# Start the server (two options shown below)
# Option A: npm start

{
  "mcpServers": {
    "eventbrite": {
      "command": "npm",
      "args": ["start"],
      "cwd": "/path/to/eventbrite-mcp",
      "env": {
        "EVENTBRITE_API_KEY": "your_api_token_here"
      }
    }
  }
}

Option B: run directly with node and built file

#else continue with the actual runtime command shown below

```json
{
  "mcpServers": {
    "eventbrite": {
      "command": "node",
      "args": ["/path/to/eventbrite-mcp/dist/index.js"],
      "cwd": "/path/to/eventbrite-mcp",
      "env": {
        "EVENTBRITE_API_KEY": "your_api_token_here"
      }
    }
  }
}

Notes:

• Replace /path/to/eventbrite-mcp with the actual path to your project.
• Ensure EVENTBRITE_API_KEY is set to your private Eventbrite token in the environment.

## Configuration and runtime details

Use the following concrete, ready-to-run configurations to connect your MCP client to the Eventbrite MCP Server. You can choose either the npm-based start method or the direct Node.js execution method.

## Claude Desktop configuration (examples)

json { "mcpServers": { "eventbrite": { "command": "npm", "args": ["start"], "cwd": "/path/to/eventbrite-mcp", "env": { "EVENTBRITE_API_KEY": "your_api_token_here" } } } }

## Alternative runtime configuration (recommended)

json { "mcpServers": { "eventbrite": { "command": "node", "args": ["/path/to/eventbrite-mcp/dist/index.js"], "cwd": "/path/to/eventbrite-mcp", "env": { "EVENTBRITE_API_KEY": "your_api_token_here" } } } }

## Testing and event viewer

You can test event retrieval and view events using the included tooling. Start the test client to verify basic retrieval, and use the events viewer to browse events locally. If the events data file does not exist, the client fetches data from Eventbrite automatically.

## Security and maintenance notes

Keep your Eventbrite API key secure and rotate it periodically. Do not expose your key in client configurations or public repositories. Use environment variables to pass sensitive data and restrict access to the MCP server to trusted clients.

## Troubleshooting

If you encounter authentication errors, verify that EVENTBRITE\_API\_KEY is valid and that the server can reach Eventbrite services over the network. Check that the MCP server process has the correct working directory and that dependencies are installed. Review environment setup to ensure your client is configured to communicate with the server endpoint.

## Notes

The server implements event listing and event detail tools first, with additional event management, attendee tools, and analytics features planned for future phases.

## Available tools

### list\_events

Fetch a list of Eventbrite events with optional filters such as date range and status.

### get\_event\_details

Retrieve detailed information for a specific event by its ID.

### create\_event

Create a new event in Eventbrite (planned tool).

### update\_event

Update details of an existing Eventbrite event (planned tool).

### publish\_event

Publish an Eventbrite event to make it visible to attendees (planned tool).

### list\_attendees

List attendees for an event and filter by status or date.

### get\_attendee\_details

Get detailed information about a specific attendee.

### export\_attendee\_data

Export attendee data for reporting or integration.

### generate\_sales\_report

Generate reports on ticket sales, revenue, and trends (planned).

### generate\_attendance\_report

Create analytics focused on attendee counts and check-ins (planned).

### generate\_analytics\_chart

Produce visual charts for key event metrics (planned).

### create\_data\_visualizations

Create charts/graphs for dashboards and reports (planned).