Eventbrite MCP

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Remote HTTP

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "eventbrite-mcp": {
      "url": "https://www.eventbrite.com"
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

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

Terminal

npm install -g @chrischall/eventbrite-mcp

Claude Code (.mcp.json):

config.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

Terminal

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/.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Eventbrite MCP

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "eventbrite-mcp": { "command": "npx", "args": ["-y", "eventbrite-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/eventbrite-mcp?style=directory)](https://allmcps.com/mcp/eventbrite-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/eventbrite-mcp"><img src="https://allmcps.com/api/badge/eventbrite-mcp?style=directory" alt="Eventbrite MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

36Quality signal: Fair · 36/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Eventbrite MCP →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

eventbrite-mcp

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

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

Terminal

npm install -g @chrischall/eventbrite-mcp

Claude Code (.mcp.json):

config.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

Terminal

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/.