Integration · MODEL CONTEXT PROTOCOL
mcp-server-ticketmaster
A Ticketmaster MCP server that provides query capabilites from the Discovery API
WHAT IT CONNECTS
What mcp-server-ticketmaster gives an AI Agent
- 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)
- Going to https://developer.ticketmaster.com/
- Creating an account or signing in
- Going to "My Apps" in your account
- Creating a new app to get your API key
- `type`: Type of search ('event', 'venue', or 'attraction')
- `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')
- Clone the repository
- Copy the example environment file:
- Add your Ticketmaster API key to `.env`
- Install dependencies:
- Build the project:
- Test with the inspector:
SECURITY
An MCP listing is not a security review
An MCP server may receive model context, credentials, local files, or permission to call external systems. Review its code, requested environment variables, network behavior, package provenance, and maintenance status before connecting it to an agent.