search_ticketmaster
Search for events, venues, or attractions on Ticketmaster
LABSCO SUMMARY
One tool covers the whole Discovery catalogue, so the context cost stays tiny and all the work happens in the arguments.
search_ticketmaster is the entire surface: type switches between events, venues and attractions, and the remaining arguments narrow the search. Ask for text output when the answer goes straight to a person, and JSON when something else has to read it.
What it is
A single-tool server over the Ticketmaster Discovery API. One call, search_ticketmaster, covers all three record types; the type argument decides which one you get back.
What you get
- Events, venues or attractions from one call — set type to event, venue or attraction
- Filters that combine: keyword, a startDate and endDate in YYYY-MM-DD, city, stateCode, countryCode
- classificationName for categories such as Sports or Music
- Direct lookups when you already hold an identifier: venueId or attractionId
- Results as structured JSON for anything downstream, or as readable text — the format argument, JSON by default
- Records come back with names and IDs, dates and times, price ranges, URLs, images, and addresses for venues
Requirements
A Ticketmaster developer API key — create an account at developer.ticketmaster.com, then an app under My Apps — supplied as TICKETMASTER_API_KEY. Runs over stdio via npx -y @delorenj/mcp-server-ticketmaster.
Setup effort
Add the configuration to your client
USE CASES
01
Finding concerts in a city on particular dates
Search events by keyword with a date range and a city or state code.
02
Seeing what is coming up at one venue
Search events filtered by the venue's own ID rather than by name.
03
Checking where an act plays next
Look the act up as an attraction, then search events by its attraction ID.
04
Browsing a whole category in a region
Filter by classificationName such as Sports or Music, plus a country or state code.
05
Producing a list someone can just read
Ask for the text format instead of JSON so the result needs no further shaping.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected. search_ticketmaster is read-only and covers events, venues and attractions through its type parameter.
Requires
- npx on PATH
- TICKETMASTER_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"ticketmaster": {
"command": "npx",
"args": [
"-y",
"@delorenj/mcp-server-ticketmaster"
],
"env": {
"TICKETMASTER_API_KEY": "<YOUR_TICKETMASTER_API_KEY>"
}
}
}
}
