Ticketmaster

What is mcp-server-ticketmaster?

mcp-server-ticketmaster is an MCP (Model Context Protocol) server designed to interact with the Ticketmaster Discovery API. It allows users to search for various Ticketmaster entities like events, venues, and attractions programmatically or through human-readable text.

How to use mcp-server-ticketmaster?

To use mcp-server-ticketmaster, you first need to install it. You can do this via Smithery using npx -y @smithery/cli install mcp-server-ticketmaster --client claude or manually with npx -y install @delorenj/mcp-server-ticketmaster. A Ticketmaster API key is required, which you can obtain from the Ticketmaster developer portal. This key needs to be configured in your MCP settings file under the env section as TICKETMASTER_API_KEY.

Once set up, the server provides a tool called search_ticketmaster. This tool accepts a type parameter (event, venue, or attraction) and various optional parameters like keyword, startDate, endDate, city, stateCode, countryCode, venueId, attractionId, classificationName, and format (json or text). You can call this tool with structured JSON arguments to perform your searches.

Key Features of mcp-server-ticketmaster

Comprehensive Search Capabilities: Search for events, venues, and attractions with flexible filtering options including keyword, date range, location (city, state, country), venue-specific, attraction-specific, and event classifications/categories.
Flexible Output Formats: Get results in structured JSON data for programmatic use or human-readable text for direct consumption.
Rich Data Output: Provides comprehensive data for search results, including names, IDs, dates, times, price ranges, URLs, images, locations, addresses, and classifications.
Easy Integration: Designed as an MCP server, making it easy to integrate with compatible clients like Claude Desktop via Smithery.

Use Cases of mcp-server-ticketmaster

Event Discovery Applications: Build applications that allow users to discover concerts, sports events, theatrical performances, and more based on various criteria.
Travel Planning Tools: Integrate event and venue search capabilities into travel planning platforms to help users find activities at their destinations.
Data Analysis: Collect and analyze Ticketmaster data for market research, trend analysis, or academic purposes.
Chatbot Integration: Power chatbots or virtual assistants with the ability to answer user queries about events and venues.
Personalized Recommendations: Develop systems that recommend events or attractions to users based on their preferences and location.

FAQ from mcp-server-ticketmaster

Q: What is an MCP server? A: An MCP (Model Context Protocol) server provides tools that can be used by AI models or other applications to interact with external services and data.

Q: Do I need a Ticketmaster API key? A: Yes, a Ticketmaster API key is required to use this server. You can obtain one from the Ticketmaster developer portal.

Q: What types of searches can I perform? A: You can search for events, venues, and attractions.

Q: Can I get the output in a human-readable format? A: Yes, you can specify the format parameter as text to receive human-readable output instead of JSON.

Q: How do I contribute to the project? A: Contributions are welcome! You can submit a Pull Request, and for major changes, it's recommended to open an issue first to discuss them.

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

Installing via Smithery

To install mcp-server-ticketmaster for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install mcp-server-ticketmaster --client claude

Manual 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 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')

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

Ticketmaster Overview