Ticketmaster MCP server
10 operations0 webhooks
Live event discovery with Ticketmaster - search events, attractions, venues and the classification tree, read any of them by ID, fetch event images, and suggest collections for a partial search term.
Try Ticketmaster with your agent
Connect Ticketmaster, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Ticketmaster on my account, then run one read-only example and show me the result.
Ticketmaster tools and triggers
Tools are what your agent can do in Ticketmaster through Corsair's MCP server. Triggers are the Ticketmaster events a routine can start from.
Events
- GetRead-only
Get one event by ID, including its dates, sales window, price ranges, images, venue and attractions
events.get
- Get ImagesRead-only
Get the images for one event by ID, with each ratio, size and URL
events.getImages
- SearchRead-only
Search events by keyword, attraction, venue, location, date, classification or onsale window, with paging and sorting
events.search
Attractions
- GetRead-only
Get one attraction by ID, including its images, classifications and aliases
attractions.get
- SearchRead-only
Search attractions (artists, teams, shows) by keyword, classification or source, with paging and sorting
attractions.search
Classifications
- GetRead-only
Get one segment, genre or sub-genre by ID, with the level below it
classifications.get
- SearchRead-only
Search the segment, genre and sub-genre tree Ticketmaster uses to classify events and attractions
classifications.search
Venues
- GetRead-only
Get one venue by ID, including its address, location, timezone, markets and images
venues.get
- SearchRead-only
Search venues by keyword, country, state or geo point, with paging and sorting
venues.search
Suggest
- GetRead-only
Suggest attractions, events, venues and products for a partial search term, as a type-ahead would
suggest.get
Connect Ticketmaster to Claude, ChatGPT or Cursor
- 1
Connect Ticketmaster in Corsair
Add your Ticketmaster API key once in Corsair. Corsair stores the credential encrypted and makes the Ticketmaster API calls for your agent, so it never goes into a prompt or a config file. Connect Ticketmaster
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Ticketmaster. On a ChatGPT personal plan, connect Ticketmaster here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. Every Ticketmaster operation only reads data, so it runs right away in every mode.
FAQ
Install corsair and @corsair-dev/ticketmaster, add the Ticketmaster plugin, and connect with an API key. Then call methods like corsair.ticketmaster.api.attractions.get() from your app. Corsair keeps each tenant isolated.
Yes. Ticketmaster requires an API key from your Ticketmaster account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Ticketmaster, GitHub, Notion, Stripe, and the rest. Trigger Ticketmaster from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for live event discovery with ticketmaster - search events, attractions, venues and the classification tree, read any of them by id, fetch event images, and suggest collections for a partial search term. Common builds include sync jobs, admin tooling, and agents that call Ticketmaster APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Ticketmaster API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/ticketmaster in the open repo. When Ticketmaster ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Ticketmaster data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Ticketmaster data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Ticketmaster on a link in Strict mode and every write waits for your approval, while destructive actions are refused. Every Ticketmaster operation only reads data, so there are no changes to approve today. You can change a link's mode at hub.corsair.dev/me.