Ticketmaster MCP Server avatar

Ticketmaster MCP Server

Pricing

Pay per event + usage

Go to Apify Store
Ticketmaster MCP Server

Ticketmaster MCP Server

MCP server + scraper for Ticketmaster. Search events, attractions, venues, suggestions and genres live from Claude, ChatGPT, Cursor and other AI agents — or run it as a classic event scraper.

Pricing

Pay per event + usage

Rating

0.0

(0)

Developer

axly

axly

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

3 days ago

Last modified

Share

Give your AI assistant live access to Ticketmaster. This actor runs as a Model Context Protocol (MCP) server, so agents like Claude, ChatGPT, Cursor, and n8n can search events, attractions and venues, fetch event details, autocomplete queries and browse the genre taxonomy — on demand, in conversation.

It also runs as a classic scraper: a normal run performs a one-shot event search and pushes rows to a dataset.

Built on Ticketmaster's official Discovery API backend (the same one the mobile app uses), so results are reliable and structured — no CAPTCHAs, no bot-detection breakage, no API-key setup.

Who it's for

  • AI builders & agents — add real-time event/venue data to a chatbot or workflow.
  • Analysts — ask "what concerts are in Chicago next month under $100?" and get structured answers.
  • App & automation developers — call the tools from n8n, Make, or custom agents.

MCP tools

ToolWhat it does
search_eventsSearch events by keyword, city, country, genre, date window or geo-radius
get_eventFull detail for a single event by ID
search_attractionsFind artists, teams and performers (with upcoming-event counts)
search_venuesFind venues with address, GPS and box-office info
suggestType-ahead across events, attractions and venues
list_classificationsBrowse the segment → genre taxonomy

Each tool returns clean, structured JSON (name, date, price range, venue + GPS, lineup, classification, image, URL).

Connect it

  1. Start the actor in Standby mode (the Apify Console gives you a Standby URL).
  2. Point your MCP client at <ACTOR_STANDBY_URL>/mcp (Streamable HTTP transport).
  3. Ask your agent to search Ticketmaster — it will call the tools automatically.

Example (Claude Desktop / Cursor MCP config):

{
"mcpServers": {
"ticketmaster": {
"url": "https://<your-standby-url>/mcp"
}
}
}

Classic run mode

Run it like any scraper with a simple input to get a dataset of events:

{ "keyword": "Taylor Swift", "countryCode": "US", "maxItems": 50 }

Example tool result (search_events)

{
"count": 1,
"results": [
{
"id": "vvG1VZ...",
"name": "Taylor Swift | The Eras Tour",
"local_date": "2026-08-16",
"price_min": 49.5,
"price_max": 449.5,
"currency": "USD",
"genre": "Pop",
"venue_name": "MetLife Stadium",
"city": "East Rutherford",
"url": "https://www.ticketmaster.com/event/..."
}
]
}

FAQ

What is MCP? The Model Context Protocol is an open standard that lets AI assistants call external tools. This actor is an MCP server exposing Ticketmaster search as tools.

Do I need a Ticketmaster API key? No — the actor ships the official app's consumer key and handles everything.

How fresh is the data? Live at call time.

Can I use it without an AI agent? Yes — run it as a classic scraper to get a dataset of events.

Which markets? US/Canada, Mexico, Australia, New Zealand, UK and Ireland via the market argument, plus any country_code filter.