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
One command plus a key — npx -y @smithery/cli install mcp-server-ticketmaster --client claude, then supply credentials