Claude Fever Event Discovery connectorWhat Claude can do in your Fever Event Discovery account.
The Claude Fever Event Discovery connector exposes 2 tools, 2 read and 0 write. One finds the cities where Fever runs events, the other searches what is on in a given city. Neither writes anything, and neither books a seat. Here is what that looks like in practice, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can search Fever
Instead of scrolling Fever's listings city by city, you tell Claude what kind of night out you want. It looks up the city, runs the search with your dates, and comes back with a shortlist: price, rating, venue, upcoming sessions and a link to each event page. Picking and paying still happen on Fever itself.
Plan a Friday in New York in one message. You ask what is on after 7pm. Claude calls search_cities to get the city code, then search_events to pull that evening's sessions, sorted by popularity or by price.
Price out a team outing. Each result carries a starting price or a free label, the visitor rating and up to three upcoming sessions. Each result also links straight to the event page on Fever, where the booking itself then happens, outside the conversation.
Check coverage before a trip. One call to search_cities tells you whether Fever operates in the place you are heading.
What it will not do: reserve a seat, buy a ticket, or search by venue name. Fever's own docs describe a venue search tool, but it is not on the connector's directory sheet. Nothing fires on its own either, since Claude only searches while it answers you. To browse the other platforms covered on the site, start from the Integrations hub.
Five words before you connect
The Claude vocabulary around this connector, in a minute.
- Connector
- The link you set up once between Claude and a service you already use, so Claude can work with it while it answers you.
- Tool
- One named capability the connector opens to Claude. Claude picks which ones to call on its own, and the directory sheet lists them.
- Authorization
- Fever's own sign-in screen, where you hand Claude the access it will use afterwards. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for before an action that changes an account, shown right in the conversation when it matters.
- MCP
- The shared standard connectors are built on. It is what lets an assistant like Claude talk to an outside service such as Fever.
Connect Fever to Claude in three steps
- 01
Find Fever in your connectors
Open Claude's settings, go to Customize, then Connectors, and look for Fever Event Discovery. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before members can sign in individually.
- 02
Start the connection
Click Connect on its row and sign in through the window Fever opens itself. If the link ever breaks, use Disconnect and connect again: that is the documented fix.
- 03
Read the authorization screen
Go through Fever's authorization screen before you approve it. The service decides what the access covers, not Claude. You can also revoke that access later from your Fever account.
The 2 tools, both read-only
Fever Event Discovery gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Two search tools, each described by Fever on its developer portal. Names stay exactly as Claude shows them.
- 2 read
What Claude looks up (2)
2 toolsTwo searches in Fever's catalog that change nothing anywhere.
search_cities
Returns the cities where Fever offers activities, along with their city codes. That code is what narrows the event search afterwards, and the tool also lets Claude browse the markets Fever covers.
search_events
Pulls the events, activities and experiences on offer in one city. Claude can limit them to a date window or a single venue, sort by popularity or price, and page through long result sets.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you.
With Fever, both tools only search, and no source describes anything that changes your account. On Team and Enterprise workspaces, owners decide whether members can let certain actions run without being asked every time. They can also restrict a connector for the whole organization, say keep reading and shut off writing, and nobody can override that from their own account. And Claude works with your Fever permissions, nothing more.
Which plans include it
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members connect. For this one's current status, check its sheet in the official directory. Worth knowing: only Fever documents this connector, and no Claude help article covers it.
Where this connector stops
A connector is not an automation. Claude calls these two tools while it answers you, and nothing runs by itself when a new event goes live.
By default, its sheet only exposes reading, but that is an observed floor, not a guarantee: an admin can open actions that no public sheet shows. The directory badge is not a security audit either, and Anthropic notes on every sheet that it does not choose a publisher's tools or vouch for how they behave. Per Fever, signing in is self-service: there is no form to fill in and nothing to request from them.
Need help connecting Fever Event Discovery to Claude?
A person reads every message.
