TI
Search

Ticketmaster MCP Server for Discovery API

Explore events, venues, and attractions with an MCP server using Streamable HTTP to connect AI models to the Ticketmaster Discovery API.

View on GitHub
Quick Install
npx -y @mochow13/ticketmaster-mcp-server

Overview

This repository provides a lightweight MCP (Model Context Protocol) server that connects AI models to the Ticketmaster Discovery API using Streamable HTTP. It sits between an LLM or agent and Ticketmaster’s Discovery endpoints, translating model-driven queries into API requests and returning structured event, venue, and attraction data in a protocol-friendly format.

The server is useful when you want your model to access live event data (search, detail lookups, venue information) without embedding the Ticketmaster API key into the model or client. It supports typical Discovery API operations and exposes them over Streamable HTTP so models that implement MCP can request and consume real-time event data safely and predictably.

Repository: https://github.com/mochow13/ticketmaster-mcp-server

Features

  • Streamable HTTP endpoints compatible with the Model Context Protocol (MCP)
  • Proxy access to Ticketmaster Discovery API resources: events, venues, attractions
  • Simple configuration via environment variables
  • Returns structured JSON responses suitable for model consumption
  • Minimal, developer-friendly codebase for extension or integration

Installation / Configuration

Clone, install dependencies, and configure your Ticketmaster API key.

  1. Clone and install:
git clone https://github.com/mochow13/ticketmaster-mcp-server.git
cd ticketmaster-mcp-server
npm install
  1. Create an environment file (copy example if provided):
cp .env.example .env
  1. Example .env (replace placeholders with real values):
TICKETMASTER_API_KEY=your_ticketmaster_api_key_here
PORT=8080
LOG_LEVEL=info
  1. Start the server:
npm start
# or, if entrypoint is index.js:
node index.js

After starting, the server listens on the configured PORT and exposes the Streamable HTTP endpoints and proxy routes to the Discovery API.

Available Resources

The server proxies the core Discovery API resources. The exact route paths are implemented in the repository; common usage patterns are shown below.

ResourceDescriptionExample query parameters
eventsSearch and fetch event detailskeyword, city, postalCode, startDateTime, endDateTime, latlong, radius, page
venuesSearch and fetch venue detailskeyword, city, postalCode, page
attractionsSearch and fetch artist/attraction infokeyword, page

Typical REST-style requests the server will forward to Ticketmaster:

  • GET /events?keyword=rock&city=Seattle
  • GET /events/{id}
  • GET /venues?keyword=stadium
  • GET /venues/{id}
  • GET /attractions?keyword=band

All responses are returned as JSON and are formatted to be easily consumable by downstream models or agents.

Use Cases

  • Chatbot augmentation: Let a conversational AI answer user questions like “What concerts are in New York this weekend?” by streaming up-to-date event lists from Ticketmaster.
  • Personal assistants and agents: Agents can search events, get venue details, and suggest itineraries with fresh data, without direct access to the Ticketmaster key.
  • Discovery and recommendation features: Build an event discovery UI that queries the MCP server from a client or model to get filtered results (by genre, date, or location).
  • Alerts and notifications: Periodically query the server for new events matching a saved profile and trigger notifications when new matches appear.
  • Research and analytics: Pull event-level or venue-level data for short-lived analysis tasks executed by an LLM or automated job.

Example Requests

Search for events (via the proxy server):

curl "http://localhost:8080/events?keyword=indie&city=Portland&page=1"

Fetch a single event by id:

curl "http://localhost:8080/events/EV123456789"

Integrating from a model or agent that speaks MCP/Streamable HTTP typically involves opening a stream to the server’s MCP endpoint and issuing structured queries (see repository examples for exact stream payloads and protocol details).

Extending and Troubleshooting

  • Add support for additional Discovery API parameters by updating the request translation layer.
  • If you hit rate limits, verify that your Ticketmaster API key has sufficient quota and consider implementing backoff or caching.
  • Check logs (configured via LOG_LEVEL) for request/response traces when debugging integrations.

For exact API routes, stream payload formats, and implementation details, refer to the source code in the repository: https://github.com/mochow13/ticketmaster-mcp-server

Tags:search