Skip to main content
Glama
mcpflow

Eventbrite MCP Server

by mcpflow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Eventbrite MCP Server

This is a Model Context Protocol (MCP) server that provides tools for interacting with the Eventbrite API. It allows AI assistants to search for events, get event details, retrieve venue information, and more.

Features

  • Search for events based on various criteria (location, date, category, etc.)

  • Get detailed information about specific events

  • Retrieve venue information

  • Get a list of event categories

Related MCP server: Agent Construct

Installation

From NPM

npm install -g @ibraheem4/eventbrite-mcp

From Source

  1. Clone this repository

  2. Install dependencies:

    npm install

  3. Build the project:

    npm run build

Development

Running in Development Mode

npm run dev

This will watch for changes in the source files, rebuild the project, and restart the server automatically.

Running the MCP Server

You can run the MCP server using the provided run script:

./run.sh

This will start the MCP server using supergateway.

Running with Inspector

To run the MCP server with the Inspector, you can use:

npm run inspector

This will start the Inspector, which provides a web interface for testing the MCP server. The Inspector will be available at http://localhost:5173.

Running Manually

You can run the MCP server manually using:

npx -y supergateway --port 1337 --stdio "./build/index.js"

Or simply use the provided run script:

./run.sh

Testing

# Run all tests
npm test

# Run tests in watch mode
npm run test:watch

# Run tests with coverage
npm run test:coverage

# Run integration tests
npm run test:integration

# Test the API directly
npm run test:api

Configuration

To use this MCP server, you need to:

  1. Obtain an Eventbrite API key from the Eventbrite Developer Portal

  2. Set up your API key in one of the following ways:

    • Create a .env file in the project root (copy from .env.example):

      EVENTBRITE_API_KEY=your_eventbrite_api_key_here

    • Or provide it as an environment variable:

      export EVENTBRITE_API_KEY=your_eventbrite_api_key_here

    • Or configure it in the MCP settings file (see below)

  3. Test your API key:

    ./test-api-key.js

  4. Configure the MCP server in your MCP settings file

For Claude Desktop App

Add the following to your ~/Library/Application Support/Claude/claude_desktop_config.json file (on macOS):

{
  "mcpServers": {
    "eventbrite": {
      "command": "npx",
      "args": ["-y", "@ibraheem4/eventbrite-mcp"],
      "env": {
        "EVENTBRITE_API_KEY": "your-eventbrite-api-key"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

For Claude Developer Environment

Add the following to your ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json file (on macOS):

{
  "mcpServers": {
    "eventbrite": {
      "command": "npx",
      "args": ["-y", "@ibraheem4/eventbrite-mcp"],
      "env": {
        "EVENTBRITE_API_KEY": "your-eventbrite-api-key"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Quick Start

If you've installed from source, you can use the provided run script:

./run.sh

This will build the project and start the MCP server.

Available Tools

search_events

Search for Eventbrite events based on various criteria.

Parameters:

  • query (string, optional): Search query for events

  • location (object, optional): Location to search around

    • latitude (number, required): Latitude coordinate

    • longitude (number, required): Longitude coordinate

    • within (string, optional): Distance (e.g., '10km', '10mi')

  • categories (array of strings, optional): Category IDs to filter by

  • start_date (string, optional): Start date in ISO format (e.g., '2023-01-01T00:00:00Z')

  • end_date (string, optional): End date in ISO format (e.g., '2023-12-31T23:59:59Z')

  • price (string, optional): Filter by 'free' or 'paid' events

  • page (number, optional): Page number for pagination

  • page_size (number, optional): Number of results per page (max 100)

get_event

Get detailed information about a specific Eventbrite event.

Parameters:

  • event_id (string, required): Eventbrite event ID

get_categories

Get a list of Eventbrite event categories.

No parameters required.

get_venue

Get information about a specific Eventbrite venue.

Parameters:

  • venue_id (string, required): Eventbrite venue ID

Available Resources

Event Details Resource

URI Template: eventbrite://events/{eventId}

Get detailed information about a specific Eventbrite event.

Example Usage

Once configured, you can ask Claude to use the Eventbrite MCP tools:

  • "Search for music events in New York next weekend"

  • "Get details about Eventbrite event with ID 123456789"

  • "What categories of events are available on Eventbrite?"

  • "Tell me about the venue with ID 987654321"

License

MIT

Available Tools

4 tools
get_categoriesA

Get a list of Eventbrite event categories

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It only states the basic action (get) and resource, with no disclosure of authentication requirements, pagination, return format, or any side effects. For a read-only list operation, minimal behavior is implied, but the description adds no extra context beyond the tool name itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler. It communicates the essential purpose efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (no parameters, no nested objects), the description is adequate for basic understanding. However, with no output schema and no annotations, it lacks details about what the list contains or whether any filtering or localisation is possible. The description is sufficient for a trivial tool but leaves some ambiguity for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description has no schema semantics to clarify. The description sufficiently indicates the operation's purpose without needing to explain parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb 'Get' and specifies the resource 'a list of Eventbrite event categories'. This unambiguously distinguishes from sibling tools (search_events, get_event, get_venue) which focus on events or venues.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context is clear: this tool is for retrieving event categories. While no explicit alternatives or exclusions are stated, the sibling tools make the use case obvious. It is implied that this should be used when category data is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_eventB

Get detailed information about a specific Eventbrite event

ParametersJSON Schema
NameRequiredDescriptionDefault
event_idYesEventbrite event ID

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It only states that it returns detailed information, but does not disclose the structure, any read-only guarantee, error behavior, or required authentication. This adds minimal behavioral context beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single 9-word sentence that is front-loaded with the action and resource. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (one parameter, no output schema), the description adequately conveys the core purpose, but 'detailed information' is vague about what fields are returned. It does not mention any prerequisites or error conditions, so it is minimally sufficient but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema fully describes event_id with 100% coverage, and there is only one parameter. The description does not add any additional meaning about the parameter, so it relies entirely on the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches detailed data for a specific Eventbrite event, with 'specific' implying a single known event rather than a search. This differentiates it from sibling tools like search_events, though it does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving details of an already-known event by ID (as seen in the schema), but it does not explicitly state when to choose this over search_events or other siblings. No when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_venueA

Get information about a specific Eventbrite venue

ParametersJSON Schema
NameRequiredDescriptionDefault
venue_idYesEventbrite venue ID

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description's 'Get information' signals a read-only operation, but it does not disclose response format, error behavior, or authentication requirements. This is minimal but not misleading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single clear sentence with no redundant words, perfectly front-loaded and efficient. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple get-by-ID tool with one parameter and no output schema, the description covers the essential purpose. It could be enhanced by indicating common venue fields returned, but the current description is sufficient for selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides 100% coverage for the sole parameter venue_id, and the description adds no additional syntax or format details beyond confirming it's a venue ID. The description's 'specific venue' aligns with the schema but offers no extra insight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Get' with the resource 'specific Eventbrite venue', clearly distinguishing it from sibling tools like search_events and get_categories. It also specifies the scope ('specific') implying retrieval by ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a specific venue ID is known, but it provides no explicit comparison to siblings or exclusions. It doesn't mention when to use search_events instead or any prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_eventsB

Search for Eventbrite events based on various criteria

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
priceNoFilter by free or paid events
queryNoSearch query for events
end_dateNoEnd date in ISO format (e.g., '2023-12-31T23:59:59Z')
locationNo
page_sizeNoNumber of results per page (max 100)
categoriesNoCategory IDs to filter by
start_dateNoStart date in ISO format (e.g., '2023-01-01T00:00:00Z')

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and does not mention pagination, default behavior, response format, rate limits, or requirements. The description is too minimal to convey how the tool behaves beyond 'searching'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler words or repetition. It is front-loaded with the action and resource. However, it is not as information-dense as it could be, relying on generic phrasing, so it doesn't earn a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, nested object, no output schema, no annotations), the description is inadequate. It doesn't mention what results look like, how pagination works, or any important operational details. The description adds only a basic purpose, leaving agents without crucial context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high (88%), so parameters are already well-documented in the schema. The description's 'various criteria' adds no specific parameter meaning. Baseline 3 applies since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a search action over Eventbrite events with filtering criteria, which distinguishes it from siblings like get_event (single event retrieval), get_categories, and get_venue. The phrase 'various criteria' is somewhat generic but the overall purpose is clear and distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'Search' - the tool is for finding events matching criteria, but there is no explicit guidance about when to use it vs alternatives or exclusions. No sibling tools are referenced, leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updatesv1.0.1
    • First observedget_categories
    • First observedget_event
    • First observedget_venue
    • First observedsearch_events
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct resource: searching events, retrieving a specific event, listing categories, and fetching venue details. There is no overlap in purpose, so an agent can easily select the correct tool.

Naming Consistency5/5

All tool names follow a clear verb_noun pattern (search_events, get_event, get_categories, get_venue). The consistency makes the toolset predictable and easy to navigate.

Tool Count5/5

With only 4 tools, the server is tightly scoped for read-only event discovery. Each tool serves a clear, necessary function and the count feels appropriate for the domain.

Completeness4/5

The toolset covers the core read operations for events, categories, and venues. It lacks a few potentially useful endpoints like searching venues or getting organizers, but for the apparent purpose of event discovery, it is nearly complete.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Related MCP Connectors

  • Mercado PagoOAuth
    com.mercadopago.mcp

    The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.

    FinanceE-commerce & RetailApp Automation
    2
  • Apideck MCPA
    dev.apideck.mcp

    Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server

    Developer Tools
    42
  • mcp-ambeeA
    com.ambeedata.api-mcp-server

    The official Model Context Protocol server for Ambee. It gives any MCP-compatible AI assistant — Claude, ChatGPT, Cursor, VS Code, Ollama, and more direct access to live air quality, pollen, and weather data. To get started, including information on signing up and obtaining your Ambee key, check out the Ambee documentation on https://docs.ambeedata.com

    AI & Machine LearningData PlatformsWeather Services
    61
  • hithereiamaliff-mcp-nextcloudOAuth
    ai.smithery

    A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…

    Cloud StorageFile SystemsWorkplace & Productivity
    237

Related MCP Servers

  • MCP API Server

    fikri2992
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.
    4
    2
    MIT

  • eventos MCP Server

    bsj-m-takigawa
    F
    license
    Not graded
    quality
    D
    maintenance
    MCP server for eventos event management platform, enabling AI assistants to manage events and tickets via API integration. Supports authentication, ticket CRUD operations, and listing with pagination.
    1
    -

  • untappd-mcp-server

    darrenjrobinson
    A
    license
    B
    quality
    B
    maintenance
    A Model Context Protocol (MCP) server that exposes the Untappd API as tools for AI agents. Enables searching venues, breweries, and beers, checking what's on tap via recent check-in feeds, and looking up user activity.
    27
    38 npm
    MIT