Ticketmaster Discovery API MCP Server Events and Venues

Overview

This MCP (Model Context Protocol) server wraps the Ticketmaster Discovery API to expose event, venue, and attraction search as machine-callable tools. It’s intended for use with LLM-based agents or other automated systems that need structured access to Ticketmaster search results (events, venues, attractions) without embedding the Ticketmaster client logic directly in the agent.

By running this server you get a small HTTP service that translates simple query parameters into Ticketmaster Discovery API requests, normalizes responses, and returns JSON suitable for tool use. That makes it easy to integrate ticket and location lookups into chatbots, recommender systems, or data pipelines.

Features

• Search Ticketmaster events, venues, and attractions
• Location-aware queries (city, postal code, lat/lon, radius)
• Pagination and result sizing
• Lightweight HTTP endpoints intended for MCP/tool integration
• Support for environment-based configuration and Docker deployment
• Caching/high-level rate-limit considerations (local server-side caching recommended)

Installation / Configuration

Clone the repository and configure your Ticketmaster API key. This example assumes a Node.js-based server (npm):

# clone
git clone https://github.com/delorenj/mcp-server-ticketmaster.git
cd mcp-server-ticketmaster

# install
npm install

# create .env
cat > .env <<EOF
TICKETMASTER_API_KEY=your_ticketmaster_api_key_here
PORT=3000
CACHE_TTL_SECONDS=60
EOF

# run
npm start

Docker example:

# build
docker build -t mcp-ticketmaster .

# run (replace API key)
docker run -e TICKETMASTER_API_KEY=your_key -p 3000:3000 mcp-ticketmaster

Environment variables

• TICKETMASTER_API_KEY (required) — your Ticketmaster Discovery API key
• PORT — HTTP port (default 3000)
• CACHE_TTL_SECONDS — optional local cache time-to-live

Available Tools / Resources

The server exposes REST endpoints intended to be used as MCP tools. Below is a concise reference of common endpoints and parameters.

Endpoints

Common query parameters

• keyword — free-text search term
• city, postalCode — location filters
• latlong — comma-separated “lat,lon”
• radius — distance in miles or km (implementation-specific)
• page, size — pagination controls
• startDateTime, endDateTime — ISO-8601 date filters

Example: simple events search (curl)

curl "http://localhost:3000/events?keyword=rock&city=Seattle&size=10"

Example: get event details

curl "http://localhost:3000/events/KovZpZA7l6A" 
# where the ID is a Ticketmaster event id returned in search responses

Resources

• Project GitHub: https://github.com/delorenj/mcp-server-ticketmaster
• Ticketmaster Discovery API docs: visit Ticketmaster Developer Portal for up-to-date API details and rate limits

Use Cases

• LLM-powered ticket assistant: An agent can call /events with a user’s natural-language request (“Find rock shows in Seattle next month”) and return a curated list of events with dates, venues, and ticket links.
• Venue lookup in a travel bot: When a user asks about venues near an address, the bot calls /venues with lat/long to present nearby theaters, stadiums, and performance halls.
• Aggregation and alerts: A backend job uses /attractions or /events to monitor new shows for specific artists or locations and notifies users when new tickets become available.
• Enrichment for search and recommendations: Combine event and venue data with internal user preferences to produce personalized show recommendations or map visualizations.

Tips and Best Practices

• Respect Ticketmaster API rate limits; implement caching and exponential backoff for retries.
• Normalize dates to ISO-8601 when passing startDateTime/endDateTime.
• When building LLM tools, wrap responses with small summaries (title, date, venue, ticket URL) for concise tool outputs.
• Secure your API key (do not embed in client-side code); use server-side environment variables or secrets management.

If you need to extend the server, the codebase is deliberately small and modular: add new endpoints or transform response fields to fit your agent/tool schema. For code examples, issue templates, or contribution guidelines, see the project repository on GitHub.