Ticketmaster Scraper
Pricing
Pay per usage
Ticketmaster Scraper
Scrapes events from Ticketmaster.com based on their categories, genres, location and date. Enhances Ticketmaster's built-in event search by searching multiple categories and genres at once. Provides dataset sorting options corresponding to the Ticketmaster's UI.
1.1 (2)
Pricing
Pay per usage
18
Total users
519
Monthly users
17
Runs succeeded
>99%
Last modified
2 years ago
You can access the Ticketmaster Scraper programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
{ "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/sse?actors=lhotanova/ticketmaster-scraper", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Configure MCP server with Scrapes events by categories, genres, location and date.
You have a few options for interacting with the MCP server:
Use
mcp.apify.comviamcp-remotefrom your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).Set up the connection directly in your MCP client UI by providing the URL
https://mcp.apify.com/sse?actors=lhotanova/ticketmaster-scraperalong with an API token (or use OAuth).Connect to
mcp.apify.comvia Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=lhotanova/ticketmaster-scraper", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.
