MCP Server for Ticketmaster

What is MCP Server for Ticketmaster?

MCP Server for Ticketmaster is a Model Context Protocol server that provides tools for discovering events, venues, and attractions through the Ticketmaster Discovery API. It is built for developers and AI assistants who need programmatic or human-readable access to Ticketmaster data.

How to use MCP Server for Ticketmaster?

Install the server with npx -y install @delorenj/mcp-server-ticketmaster, then configure your Ticketmaster API key in your MCP settings file under the env section. Use the provided tool search_ticketmaster with required type parameter (event, venue, or attraction) and optional filters such as keyword, date range, city, state code, country code, venue ID, attraction ID, classification name, and output format (json or text).

Key features of MCP Server for Ticketmaster

• Search events, venues, and attractions with flexible filtering
• Filter by keyword, dates, location, venue, or attraction
• Specify event classifications or categories (e.g., Sports, Music)
• Output results as structured JSON or human-readable text
• Retrieve comprehensive data: names, IDs, dates, prices, URLs, images, addresses

Use cases of MCP Server for Ticketmaster

• Find upcoming concerts in a city within a date range
• Get detailed venue information including address and location
• Look up attractions by keyword for event planning
• Automate event discovery for content generation or recommendations

FAQ from MCP Server for Ticketmaster

How do I get a Ticketmaster API key?

Go to https://developer.ticketmaster.com/, create an account or sign in, go to "My Apps", and create a new app to obtain your API key.

What parameters does the search_ticketmaster tool require?

The only required parameter is type (event, venue, or attraction). All other parameters such as keyword, date range, location, venue ID, attraction ID, classification name, and format are optional.

What output formats are supported?

Two output formats are available: json for structured programmatic use (default) and text for human-readable consumption.

Does the server require any external dependencies?

The server is installed via npx, which implies a Node.js runtime environment. You also need an active Ticketmaster API key to authenticate requests.

Where does the data come from and what limits apply?

Data comes directly from the Ticketmaster Discovery API. The README does not specify rate limits or data restrictions beyond requiring an API key.