- Explore MCP Servers
- ticketmaster
Ticketmaster
Overview
What is Ticketmaster
The MCP Server for Ticketmaster is a server framework that interacts with the Ticketmaster Discovery API to help users find events, venues, and attractions through flexible search features.
Use cases
Users can leverage this server to search for concerts, sports events, or local attractions using various filters such as keywords, dates, and locations, making it suitable for both personal and commercial applications in event planning and marketing.
How to use
To use the server, users need to install it using npm, configure it with their Ticketmaster API key in the settings file, and then utilize the search_ticketmaster
tool by providing required and optional parameters for their specific search needs.
Key features
Key features include keyword searching, date filtering, location-specific searches, venue and attraction filtering, and the ability to output structured JSON data or human-readable text, making it highly versatile for developers and end-users.
Where to use
This MCP server is ideal for integration in applications dealing with event discovery, ticketing platforms, tourism services, or any other context where users need to find and explore events and attractions in a specific region.
Content
MCP Server for Ticketmaster
A Model Context Protocol server that provides tools for discovering events, venues, and attractions through the Ticketmaster Discovery API.
Features
- 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)
Installation
npx -y install @delorenj/mcp-server-ticketmaster
Configuration
The server requires a Ticketmaster API key. You can get one by:
- 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
Set your API key in your MCP settings file:
{
"mcpServers": {
"ticketmaster": {
"command": "npx",
"args": [
"-y",
"@delorenj/mcp-server-ticketmaster"
],
"env": {
"TICKETMASTER_API_KEY": "your-api-key-here"
}
}
}
}
Usage
The server provides a tool called search_ticketmaster
that accepts:
Required Parameters
type
: Type of search (‘event’, ‘venue’, or ‘attraction’)
Optional Parameters
keyword
: Search termstartDate
: Start date in YYYY-MM-DD format (for events)endDate
: End date in YYYY-MM-DD format (for events)city
: City namestateCode
: State code (e.g., ‘NY’)countryCode
: Country code (e.g., ‘US’)venueId
: Specific venue IDattractionId
: Specific attraction IDclassificationName
: Event category (e.g., ‘Sports’, ‘Music’)format
: Output format (‘json’ or ‘text’, defaults to ‘json’)
Examples
Structured JSON Output (Default)
<use_mcp_tool> <server_name>ticketmaster</server_name> <tool_name>search_ticketmaster</tool_name> <arguments> { "type": "event", "keyword": "concert", "startDate": "2025-02-01", "endDate": "2025-02-28", "city": "New York", "stateCode": "NY" } </arguments> </use_mcp_tool>
Human-Readable Text Output
<use_mcp_tool> <server_name>ticketmaster</server_name> <tool_name>search_ticketmaster</tool_name> <arguments> { "type": "event", "keyword": "concert", "startDate": "2025-02-01", "endDate": "2025-02-28", "city": "New York", "stateCode": "NY", "format": "text" } </arguments> </use_mcp_tool>
Development
- Clone the repository
- Copy the example environment file:
cp .env.example .env
- Add your Ticketmaster API key to
.env
- Install dependencies:
npm install
- Build the project:
npm run build
- Test with the inspector:
npm run inspector
Contributing
Contributions are welcome! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.
License
MIT License - see LICENSE file for details