Spark
Sign In
MCP Connector

Query Ticketmaster Events and Venues

MCP server exposing Ticketmaster's Discovery API - search events, venues, and attractions by keyword, date, and location.

Connect
Works with ticketmaster
delorenj
Own this? Claim it
91
Spark score
out of 100
Updated Jul 2025
Fresher alternatives ↓
Version 1.0.0
Models
universal
Add to Favorites

Why it matters

Access and query the Ticketmaster Discovery API to retrieve detailed information about events, venues, and attractions. This asset enables flexible searching with various filtering options and provides structured data for programmatic use.

Outcomes

What it gets done

01

Search for events, venues, and attractions using keywords and classifications.

02

Filter search results by date range, location, and specific IDs.

03

Retrieve comprehensive event details including names, dates, prices, and URLs.

04

Output search results in both structured JSON and human-readable text formats.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-ticketmaster | bash

Capabilities

Tools your agent gets

search_ticketmaster

Search for events, venues, and attractions with flexible filtering options including keywords, dates, and locations.

Overview

Ticketmaster MCP Server

An MCP server exposing Ticketmaster's Discovery API as one search_ticketmaster tool for finding events, venues, and attractions by keyword, date, location, or classification. Use when an agent needs to answer live-event, venue, or attraction discovery questions for a user, in either JSON or plain text.

What it does

This MCP server wraps the Ticketmaster Discovery API in a single tool, search_ticketmaster, that lets an MCP client search for events, venues, or attractions with flexible filters - keyword, date range, city/state/country, a specific venue or attraction ID, or an event classification like "Sports" or "Music". Results come back as either structured JSON for programmatic use or human-readable text, and include names, IDs, URLs, images, dates and price ranges for events, addresses for venues, and category classifications for attractions.

When to use - and when NOT to

Use this connector when an agent needs to answer questions about live events, find venues in a given city, or look up attractions - for example, "what concerts are in New York this month" or details on a specific venue. It is read-only discovery against Ticketmaster's public catalog; it does not book tickets, check seat availability, or process purchases, and every request is scoped by the required type parameter (event, venue, or attraction), so a single call answers one of those three categories at a time rather than mixing them.

Capabilities

The search_ticketmaster tool takes a required type plus optional keyword, startDate/endDate (YYYY-MM-DD, for events), city, stateCode, countryCode, venueId, attractionId, classificationName, and format (json or text, defaulting to json). Event results include date/time and price range; venue results include location and address; attraction results include classification data - all searches can be narrowed by keyword and geography regardless of type.

How to install

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

or manually via npx -y install @delorenj/mcp-server-ticketmaster. Either way it requires a TICKETMASTER_API_KEY, obtained by creating a free developer account at developer.ticketmaster.com and registering an app under "My Apps", set in the MCP settings file:

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

Who it's for

Agents and assistants that need to answer live-events questions - concert and show listings, venue lookups, attraction details - for a user in a given city or date range, without the developer building a direct Ticketmaster API integration themselves. It also suits developers who want to extend the server itself: the project ships with a local development workflow (clone, copy .env.example to .env, add the API key, npm install, npm run build, and npm run inspector to test tool calls interactively) for anyone adding new search filters or output formats on top of the existing search_ticketmaster tool.

Source README

MCP Server for Ticketmaster

smithery badge

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

Server for Ticketmaster Events MCP server

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)

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

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.