Claude StubHub connectorWhat Claude can look up on StubHub.
The Claude StubHub connector exposes 3 tools, all of them read. 0 write tools, 0 undocumented ones. Below: how Claude goes from a performer's name to one exact seat, what the sheet doesn't show, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when you're hunting for seats
Rather than juggling tabs to compare dates, prices and sections, you name an event, a performer or a genre in the conversation. Claude queries StubHub, finds the event, then shows the tickets on sale with prices, seat locations and the venue map, all without leaving the chat.
Pin down the right event. event_search handles a specific performer, team or venue just as well as a broad category, genre or type of show. It's always the first step when no event has been identified yet.
Compare what's on sale. Once the event is found, fetch_listings shows prices, seat locations, the venue map and view-from-seat photos, so you can trade off price against sightlines.
Look closely at one offer. highlight_listing isolates a single listing already shown, with its exact price, the seat and a static photo of the view.
According to its sheet, StubHub claims over 50 million listings in more than 200 countries. What the sheet doesn't show: none of the three tools is flagged as a write tool, and no source describes completing a purchase inside Claude. Nothing runs by itself either, no alert fires when a price drops. That sort of watching is an automation tool's job, a different trade; the Integrations hub covers that side.
The vocabulary in one minute
Five words you'll see while connecting StubHub.
- Connector
- The link you set up once between Claude and an outside service, so Claude can draw on it while it is answering you.
- Tool
- One named action a connector opens to Claude. Claude picks it on its own as it answers, and the directory sheet lists each tool by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will rely on. Granted once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before finishing an action that changes an account, shown in the conversation right when it counts.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude hold a conversation with an outside service.
Connect StubHub to Claude in three steps
- 01
Find StubHub in Claude
In Claude's settings, open Customize, then Connectors, and spot StubHub in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first so that members can use it.
- 02
Start the connection
Click Connect on its row. If the service asks you to identify yourself, StubHub opens that sign-in window itself. Should the link break one day, use Disconnect and then connect it again.
- 03
Read the authorization screen
When an authorization screen appears, read it before accepting: it belongs to the service, not Claude, and it sets what the access covers. Anything granted there can also be withdrawn from the service itself.
The 3 tools in the Claude StubHub connector
StubHub gives Claude 3 tools: 3 that read your account, 0 that change something in it.
All three tools sit on the reading side. Their names stay exactly as Claude shows them.
- 3 read
What Claude reads (3)
3 toolsThree tools that look up the ticket market, from broad to precise.
event_search
Finds the concerts, games, plays or shows matching your request, whether it names someone specific or a whole genre. That's how Claude gets the event ID the other two tools depend on.
fetch_listings
Displays the listings for an event already identified: prices, seat locations, the venue map and photos taken from the seat. You compare the options side by side in the chat.
highlight_listing
Zooms in on a single listing spotted in the previous results, with its exact price, the seat and a static view photo, in more detail than the overview.
What Claude asks you before acting
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. All three StubHub tools are flagged as reading.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked again. They can also cap what a connector may do across the organisation, and nobody gets around that setting from their own account. Claude never gets more than the access of the person who connected the connector, whatever the request. A connector an owner has closed stays closed even if a member asks for it again in the conversation.
Which plans it's available on
None of the 819 sheets in the official directory gives availability by plan. For StubHub as for the others, that answer isn't published anywhere, connector by connector.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns them on for the organisation before members connect. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector isn't an automation: Claude calls these tools while it answers you, and nothing starts on its own when a new date is announced. Only the publisher documents this connector.
By default the sheet shows only reading, and that's an observed floor, not a guarantee: an administrator can open actions missing from every public sheet. The directory's partner badge isn't a security audit, and Anthropic says so on every sheet: it doesn't choose a publisher's tools or vouch for their behaviour. Connect only what comes from a publisher you know. Other connectors are listed on the Claude integrations page.
Need help connecting StubHub to Claude?
A person reads every message.