Ticketmaster

You have a Model Context Protocol (MCP) server that exposes Ticketmaster Discovery data. It helps you discover events, venues, and attractions with flexible filters, and presents results in both structured JSON for apps and human-readable text for quick insights. This server is useful for building event dashboards, search tools, or integrations that need up-to-date Ticketmaster data.

How to use

You interact with the Ticketmaster MCP server by running its search tool from an MCP client. The tool is designed to accept a variety of filters so you can narrow results to events, venues, or attractions. Practical use cases include finding concerts in a city during a date range, locating venues by location, or filtering events by category. You can choose the output format to match your needs: use JSON for downstream processing or text for direct human reading. The server returns comprehensive data such as names, IDs, dates, prices, URLs, images, and locations.

Typical workflows you might adopt:

• Search for events by keyword within a date window and city to build a local events feed.
• Retrieve venue or attraction details to populate a directory.
• Combine multiple searches to create a tailored recommendations screen.

How to install

Prerequisites: ensure you have Node.js and npm installed on your system.

Install the MCP server package using the recommended one-line command.

Run the server or integrate it through your MCP client configuration. The server requires a Ticketmaster API key to function.

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

Configuration

The server needs a Ticketmaster API key. Obtain the key from Ticketmaster Developer Portal by creating an app under My Apps.

Configure your MCP settings to include the Ticketmaster server. Use the following snippet as the configuration for the MCP server entry.

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

Notes and tips

The server exposes a tool named search_ticketmaster you can call through your MCP client. This tool accepts a required type parameter (event, venue, or attraction) and optional filters such as keyword, startDate, endDate, city, stateCode, countryCode, venueId, attractionId, classificationName, and format (defaults to JSON). Use format: "text" to receive human-readable output.

Available tools

search_ticketmaster

Tool to search Ticketmaster data. Requires a type (event, venue, or attraction) and supports filters such as keyword, date range, location, and classification. Output can be JSON or text.