Ticketmaster

Search Ticketmaster's live event catalog and browse ticket prices.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Ticketmaster connector does

The Ticketmaster MCP server connects Ticketmaster's live event catalog to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists two tools, both of them searches. Nothing on this connector buys a ticket, holds a seat or takes a payment — Ticketmaster states the assistant does not process payment, and every result ends in a link you follow.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Ticketmaster tools (2)

  • find_tickets
  • unified_search

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • It cannot buy, reserve, pay for or cancel anything. Ticketmaster states the assistant does not process payment and that purchases complete on Ticketmaster. Every result terminates in a link you follow.
  • Ticketmaster publishes no tool list. The two names come from Anthropic's directory and could not be diffed against a vendor enumeration, because none exists. Ticketmaster's own connector page never prints either name.
  • We could not verify the auth posture live. Anthropic's directory records the endpoint as authless with an auth posture of no auth, and Ticketmaster says no account is needed to search — but both are claims *about* the server, not our observation of it. Our single anonymous initialize request returned HTTP 403 from a Varnish edge cache with an HTML error body and no WWW-Authenticate header, which is an edge block rather than an authentication challenge. authVerified is therefore false on this page.
  • No scope document is readable. Four probes for RFC 9728 and OAuth metadata each returned the same 437-byte Varnish 403 as a deliberately nonsensical control path, differing only in the cache-node identifier the error prints. No scopes_supported value was observed either way, so no boundary between reading and any other operation is claimed or refuted.
  • We could not read any tool schema or safety annotation. No parameter name for either tool appears anywhere we could find.
  • Whose credential the server presents is undocumented. Ticketmaster's APIs authenticate by an API key issued to a registered developer or partner, passed as an apikey parameter or an x-api-key header — a company credential carrying no user identity. No document states whether this connector calls under such a key or under something else, so who bears the quota and terms consequences of a call is unresolved.
  • Terms restrict what you may do with the data. Ticketmaster's API Terms of Use forbid caching or storing Event Content other than for reasonable periods needed to provide your service, forbid selling or deriving revenue from API access, and forbid applications that replicate the essential user experience of Ticketmaster.com. They also require removing Event Content within 24 hours of an owner's request. Building a product on connector output is a licensing question, not just a technical one.
  • No rate limit is published for the MCP endpoint, and Ticketmaster's own two figures disagree. The getting-started page states 5,000 calls per day at 5 requests per second; the developer FAQ states 5,000 per day at 2 requests per second. Both describe the public API, not this endpoint, and we found no statement that the MCP server shares either quota.
  • One Ticketmaster documentation path is dead, and the real one is elsewhere. The path /support/partner-api-terms-of-use/ redirects to a 404 page. The Partner API Terms of Use do exist, at /support/terms-of-use/partner/, and repeat the General Terms' restrictions verbatim. The developer portal's sitemap is also stale: it lists 19 URLs, most with a 2016 last-modified date, and omits the Partner API FAQ and the current Discovery v2 path entirely.
  • Ticketmaster's terms say nothing about AI agents. Neither Terms of Use nor the developer FAQ contains AI-, LLM- or model-specific language; the General Terms were last updated in June 2023. The applicable clauses are generic ones — no automated content, no concealing your application's identity, and rate limiting for calls not primarily in response to direct user actions. Read them as covering the case by implication, not by name.
  • Prices and availability move fast. Ticketmaster states results reflect what is actually on sale right now. For a high-demand onsale, a snapshot in a conversation can be stale by the time you follow the link.
  • The consumer Terms of Use could not be read. Ticketmaster's fan-facing terms render entirely client-side; the fetched HTML carries no __NEXT_DATA__, RSC flight payload or embedded JSON block, so its clauses on automation and ticket limits are not reported here. That is an extractor failure on our side, not evidence Ticketmaster published nothing.

Frequently asked questions

Can Claude actually buy Ticketmaster tickets for me?

No. Ticketmaster's own connector page states plainly that purchases complete on Ticketmaster and that the assistant does not process payment. Both listed tools are searches. When you pick a ticket the connector hands you a link, and you sign in and check out on Ticketmaster's site exactly as you normally would.

Do I need a Ticketmaster account to use the MCP connector?

Not to search. Ticketmaster states no account is required and that you can browse events and ticket prices right away. An account becomes necessary only at checkout, which happens on Ticketmaster's own website after you follow the link. Anthropic's directory also records this endpoint as authless with no auth posture.

How many tools does the Ticketmaster MCP server have?

Anthropic's directory lists two, find_tickets and unified_search. That is the only enumeration anywhere. Ticketmaster's connector documentation never prints a machine tool name, describing capabilities only in prose such as finding events and browsing tickets. We could not run an anonymous handshake, so two is unverified rather than confirmed.

Why is the Ticketmaster MCP endpoint on a partner-mcp hostname?

Because it sits alongside Ticketmaster's Partner API, its commerce tier. Ticketmaster describes that API as letting clients reserve, purchase and retrieve ticket information, and restricts it to companies with existing official distribution relationships. None of those purchase operations appears in this two-tool MCP listing, but the hostname names the neighbourhood.

What data does Ticketmaster receive when I use the connector?

Your search terms. Ticketmaster's connector page states that the search terms from your request, such as the artist, city or event you are looking for, are sent to Ticketmaster to return matching results. Your use is governed by the Ticketmaster Privacy Policy. Because no sign-in happens, no account identity travels with the query.

Are ticket prices from the connector accurate?

They reflect live inventory at the moment of the search. Ticketmaster states everything runs on its real inventory, so availability and prices reflect what is actually on sale right now. Event tickets move faster than most goods, so treat any quoted price in a conversation as a snapshot to confirm at checkout, not an offer.

Can I use Ticketmaster event data from the connector in my own app?

Not freely. Ticketmaster's API Terms of Use forbid caching or storing Event Content beyond reasonable periods needed to provide your service, forbid deriving revenue from API access, and forbid applications replicating the essential user experience of Ticketmaster.com. Commercial redistribution runs through the affiliate or partner programs, not through this connector.

Are there rate limits on the Ticketmaster MCP server?

None are published for the connector itself, and Ticketmaster's two published figures disagree. Its getting-started page states a default quota of 5,000 calls per day and 5 requests per second; its developer FAQ states 2 requests per second and 5,000 per day. Whether the MCP endpoint inherits either quota is undocumented.

Sources

More E-commerce connectors

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Ticketmaster to work.

Connect Ticketmaster once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.