Skip to main content
Glama
MCP Server for Ticketmaster Events

MCP Server for Ticketmaster Events

by delorenj

MCP Server for Ticketmaster

A Model Context Protocol server that provides tools for discovering events, venues, and attractions through the Ticketmaster Discovery API.

Features

  • Search for events, venues, and attractions with flexible filtering:

    • Keyword search

    • Date range for events

    • Location (city, state, country)

    • Venue-specific searches

    • Attraction-specific searches

    • Event classifications/categories

  • Output formats:

    • Structured JSON data for programmatic use

    • Human-readable text for direct consumption

  • Comprehensive data including:

    • Names and IDs

    • Dates and times (for events)

    • Price ranges (for events)

    • URLs

    • Images

    • Locations and addresses (for venues)

    • Classifications (for attractions)

Related MCP server: Ticketmaster Partner API

Installation

Installing via Smithery

To install mcp-server-ticketmaster for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install mcp-server-ticketmaster --client claude

Manual Installation

npx -y install @delorenj/mcp-server-ticketmaster

Configuration

The server requires a Ticketmaster API key. You can get one by:

  1. Going to https://developer.ticketmaster.com/

  2. Creating an account or signing in

  3. Going to "My Apps" in your account

  4. Creating a new app to get your API key

Set your API key in your MCP settings file:

{
  "mcpServers": {
    "ticketmaster": {
      "command": "npx",
      "args": ["-y", "@delorenj/mcp-server-ticketmaster"],
      "env": {
        "TICKETMASTER_API_KEY": "your-api-key-here"
      }
    }
  }
}

Usage

The server provides a tool called search_ticketmaster that accepts:

Required Parameters

  • type: Type of search ('event', 'venue', or 'attraction')

Optional Parameters

  • keyword: Search term

  • startDate: Start date in YYYY-MM-DD format (for events)

  • endDate: End date in YYYY-MM-DD format (for events)

  • city: City name

  • stateCode: State code (e.g., 'NY')

  • countryCode: Country code (e.g., 'US')

  • venueId: Specific venue ID

  • attractionId: Specific attraction ID

  • classificationName: Event category (e.g., 'Sports', 'Music')

  • format: Output format ('json' or 'text', defaults to 'json')

Examples

Structured JSON Output (Default)

<use_mcp_tool>
<server_name>ticketmaster</server_name>
<tool_name>search_ticketmaster</tool_name>
<arguments>
{
  "type": "event",
  "keyword": "concert",
  "startDate": "2025-02-01",
  "endDate": "2025-02-28",
  "city": "New York",
  "stateCode": "NY"
}
</arguments>
</use_mcp_tool>

Human-Readable Text Output

<use_mcp_tool>
<server_name>ticketmaster</server_name>
<tool_name>search_ticketmaster</tool_name>
<arguments>
{
  "type": "event",
  "keyword": "concert",
  "startDate": "2025-02-01",
  "endDate": "2025-02-28",
  "city": "New York",
  "stateCode": "NY",
  "format": "text"
}
</arguments>
</use_mcp_tool>

Development

  1. Clone the repository

  2. Copy the example environment file:

    cp .env.example .env
  3. Add your Ticketmaster API key to .env

  4. Install dependencies:

    npm install
  5. Build the project:

    npm run build
  6. Test with the inspector:

    npm run inspector

Contributing

Contributions are welcome! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.

License

MIT License - see LICENSE file for details

Available Tools

1 tool
search_ticketmasterC

Search for events, venues, or attractions on Ticketmaster

Inputs: type (required), keyword, startDate, endDate, +7 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as searching for events, venues, or attractions, making it straightforward for an agent to understand its function without confusion.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'search_ticketmaster' follows a clear verb_noun pattern, which would be consistent if more tools were added, but as a standalone, it sets a good precedent.

    Tool Count2/5

    A single tool is too few for a server focused on Ticketmaster events, which typically involves operations like browsing events, getting details, checking availability, or purchasing tickets. This minimal set feels thin and incomplete for the apparent scope, limiting agent capabilities.

    Completeness2/5

    The tool surface is severely incomplete for the domain of Ticketmaster events. While search is a useful starting point, there are obvious gaps such as retrieving event details, listing venues, checking ticket availability, or handling bookings, which are essential for comprehensive event management workflows.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables users to search for events, performers, and venues through the SeatGeek API. Provides event recommendations, detailed venue seating information, and performer discovery capabilities for ticketed entertainment events.
      4
      76 npm
      3
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables discovery and search of Ticketmaster events, venues, and attractions with advanced filtering options including date ranges, location-based search, and event classifications through the Ticketmaster Partner API.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and retrieve live Ticketmaster Discovery v2 data, including events, venues, attractions, classifications, images, and autocomplete suggestions. Supports filtering by keyword, location, date ranges, and market for event discovery.
      311 npm
      1
      MIT