Yes, Eventbrite is free to use.

How do I install Eventbrite?

Eventbrite is a local plugin. Install it using npm package: @chrischall/eventbrite-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Eventbrite safe to use?

Yes. Eventbrite passed MCP Marketplace's automated security scan with a score of 9.1/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Eventbrite need?

Eventbrite requires the following credentials or environment variables: EVENTBRITE_TOKEN. You can find setup instructions on the server detail page.

What AI apps work with Eventbrite?

Eventbrite uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Eventbrite MCP Server

by Chris Hall

Developer ToolsLow Risk9.1Local

Free

Eventbrite for Claude — your tickets/orders, organizer data, and public event discovery

About

Eventbrite for Claude — your tickets/orders, organizer data, and public event discovery

Security Report

9.1

Low Risk9.1Low Risk

Valid MCP server (1 strong, 1 medium validity signals). 2 known CVEs in dependencies (0 critical, 1 high severity) Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (75/76 approved).

4 files analyzed · 3 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Personal OAuth token (eventbrite.com/platform/api-keys); needed for account toolsRequired

Environment variable: EVENTBRITE_TOKEN

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-chrischall-eventbrite-mcp": {
      "env": {
        "EVENTBRITE_TOKEN": "your-eventbrite-token-here"
      },
      "args": [
        "-y",
        "@chrischall/eventbrite-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

eventbrite-mcp

This project was developed and is maintained by AI (Claude Code). Use at your own discretion.

MCP server for Eventbrite: your tickets and orders, organizer data (events, attendees, orders), any public event by id, and public event search — which Eventbrite removed from its documented API in 2019 and now only exists on the consumer site.

Two data paths, matched to how Eventbrite is reachable:

Documented API (eventbriteapi.com/v3) — plain server-side HTTPS with a personal OAuth token (EVENTBRITE_TOKEN, free: create one). Powers the account, organizer, event-by-id, and reference tools.
Consumer discovery API (www.eventbrite.com/api/v3/destination/…) — the site WAF-blocks server-side clients, so search routes through your own signed-in eventbrite.com browser tab via the fetchproxy bridge (Transporter extension), reusing your authenticated session. Powers eb_search_events, eb_resolve_place, eb_event_details, eb_healthcheck.

All tools are read-only.

Setup

npm install -g @chrischall/eventbrite-mcp

Claude Code (.mcp.json):

{
  "mcpServers": {
    "eventbrite": {
      "command": "eventbrite-mcp",
      "env": { "EVENTBRITE_TOKEN": "your-private-token" }
    }
  }
}

Without EVENTBRITE_TOKEN the server still boots; account tools error helpfully on first use, and discovery tools work regardless.
For discovery tools: install the Transporter extension, keep an eventbrite.com tab open, and approve the one-time pair prompt (the prompt covers the csrftoken cookie read the search POST needs). Run eb_healthcheck to verify the hop.

Tools

Tool	Path	Notes
`eb_me`	token	your profile
`eb_my_orders`	token	your tickets, event expanded
`eb_my_organizations`	token	organizer orgs
`eb_org_events` / `eb_org_attendees` / `eb_org_orders`	token	organizer data
`eb_org_venues` / `eb_org_discounts` / `eb_org_ticket_groups` / `eb_org_webhooks`	token	org-scoped collections
`eb_org_report`	token	sales / attendees analytics, date-windowed
`eb_event` / `eb_event_description`	token	any public event by id
`eb_ticket_classes` / `eb_ticket_class`	token	an event's ticket types
`eb_event_attendees` / `eb_event_attendee`	token	per-event attendees (`changed_since` polls incrementally)
`eb_event_orders`	token	per-event orders
`eb_event_questions`	token	registration questions (`canned: true` for the standard bank)
`eb_order`	token	a single order by id
`eb_venue` / `eb_venue_events`	token	venue detail and its events
`eb_organizer` / `eb_organizer_events`	token	organizer profile and everything they run
`eb_series_events`	token	occurrences of a recurring series
`eb_user`	token	a public user profile
`eb_reference`	token	categories / subcategories / formats / timezones / countries / regions
`eb_resolve_place`	token	location → place id (`Charlotte, NC` → `85981333`), plus browse shelves
`eb_search_events`	token	the consumer search; `compact: true` for slim results, `aggs` for facets
`eb_event_details`	token	batch event detail
`eb_healthcheck`	bridge	bridge diagnostics (stdio only; the bridge is a fallback route)

Search flow: eb_resolve_place {location: "Charlotte, NC"} → eb_search_events {q: "blues", place_id: "85981333", compact: true}.

eb_resolve_place also accepts a raw slug (nc--charlotte). A bare city with no state or country is rejected rather than guessed.

Development

npm install
npm test          # node suite
npm run build     # tsc + esbuild bundle

API shape notes (captured + verified): docs/EVENTBRITE-API.md. A shell-level access skill (curl + fpx, no server needed) ships in skills/eventbrite/.