Claude Kiwi.com connectorWhat Claude can do with Kiwi.com flight search.
The Claude Kiwi.com connector exposes 2 tools. 1 reads flight offers from Kiwi.com, 1 sends a message out to its developers, and none is left undocumented. Below: what Claude can look up, where booking actually happens, and who controls the connector.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can search Kiwi.com
Instead of filling in a search form, juggling date pickers and comparing tabs, you describe the trip in a sentence and Claude queries Kiwi.com itself. It names cities or airports as you said them, handles one-way or return trips, and lays the options out in the conversation with a link to book each one.
Price a weekend before you commit. Someone planning two nights in Lisbon asks for return flights from Lyon on given dates: Claude calls search-flight and brings back the matching offers, each with a link to book it.
Plan for a whole family. Two adults, a child and an infant, economy or business: the publisher says the search takes the number and type of passengers and every cabin class, so the answer matches the party that actually travels.
Stretch the dates. When the calendar is loose, Kiwi.com lets the search widen by up to 3 days on either side, instead of sticking to the exact date you had in mind.
Now what the connector does not do. Claude does not book or pay: each result carries a link, and the booking itself happens on Kiwi.com. Nothing runs on its own either, so no tool watches a route and warns you when a price drops; Claude only searches while it answers you. If you want that kind of recurring check, it is the job of an automation tool, and the Integrations hub lists the platforms that do it.
Five words before you connect
The vocabulary around this connector, in one minute.
- Connector
- A link you set up once between Claude and an outside service, so Claude can use that service while it answers you in the chat.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs by itself, and the directory sheet lists each by name.
- Approval
- The confirmation Claude waits for before it goes ahead with an action, shown in the conversation at the moment it matters.
- Directory
- The official catalogue where every connector has a sheet with its publisher, its purpose and the list of tools it exposes.
- MCP
- The open standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Kiwi.com.
Connect Kiwi.com to Claude in three steps
- 01
Find Kiwi.com in Claude
Open Claude's settings, go to Customize then Connectors, and look Kiwi.com up in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables it for the organization before members can each connect.
- 02
Start the connection
Click Connect on the Kiwi.com row and follow the window the service opens on its own side. If the link breaks later, Disconnect it and connect again from the same row; that is the documented fix.
- 03
Read the authorization screen
Look at the screen that appears before you accept it. It belongs to the service, not to Claude, and it is what defines the access. Whatever it lists, Claude still asks before each action by default.
The 2 tools, split by what they do
Kiwi.com gives Claude 2 tools: 1 that read your account, 1 that change something in it.
One tool reads flight offers, one sends a message out. Names stay exactly as Claude shows them.
- 1 read
- 1 write
What Claude reads (1)
1 toolOne tool that looks up flights and changes nothing.
search-flight
Queries Kiwi.com for flights between two places on your dates for your group of travellers, turning city names into airports by itself. Each result comes with a booking link to the chosen flight.
What Claude sends (1)
1 toolOne tool that sends something outside the conversation. No source details its confirmation, so the general rule below applies.
feedback-to-devs
Approval: see the rulePasses a bug report, a remark or a feature request about flight search straight to the developers who build the Kiwi.com connector. The message leaves the conversation and reaches their team.
What Claude checks with you first
By default, Claude stops and asks for confirmation before each action it takes on someone's behalf. The request shows up in the chat when it is relevant.
On Team and Enterprise workspaces, owners decide whether a member may let some actions go through without being asked again. They can also bound what a connector may do for the whole organization, for instance leaving lookups open and closing anything that sends. That setting binds everyone, and nobody lifts it from a personal account. Claude also acts with the rights of the person who connected, nothing more.
Which plans include it
None of the 819 sheets in the official directory shows its plan availability. That answer is published nowhere, connector by connector.
What Anthropic does publish is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. For the live state, check the Kiwi.com sheet in the directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing fires when a fare changes or a seat opens up.
Only Kiwi.com documents this connector: neither the Claude help center nor Anthropic's developer docs has a page about it. The tool list is an observed floor, not a promise, since an administrator can open actions that appear on no public sheet. The partner badge in the directory is not a security audit, and Anthropic states on each sheet that it neither picks the tools a publisher exposes nor guarantees how they behave.
Need help connecting Kiwi.com to Claude?
A person reads every message.