Claude Booking.com connectorWhat Claude can do in your Booking.com account.
The Claude Booking.com connector exposes 1 tool. That single tool reads Booking.com search results, 0 tools write anything, and 0 are left undocumented. Below: what Claude can find for you, why it never books or pays, and who in your organization can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can search Booking.com
Instead of opening Booking.com, typing a city, setting dates and ticking filters one by one, you describe the trip to Claude in plain words. It runs the search on Booking.com, reads what comes back and hands you a short list you can discuss, narrow down and compare, all inside the same conversation.
A shortlist from one sentence. Tell Claude the destination, the dates and how many people travel, and accommodations_search brings back a shortlist of matching stays, each one ready to open on Booking.com for the full details.
Filters said out loud. Breakfast included, a higher rating, an apartment rather than a hotel: facilities, ratings, accommodation type and meal plans are the filters Booking.com documents for the connector, so you stop hunting for checkboxes.
A comparison in the same thread. Booking.com presents the connector as a way to search and compare stays, so you can weigh the shortlist with Claude before opening a single page.
What it will not do: Claude does not reserve a room, pay, change a reservation or open your Booking.com account. Every reservation ends on the Booking.com site, and nothing runs on its own while you are away from the chat. To see how other publishers shape their connectors, the Integrations hub lists the families covered on this site.
Five words to know first
The Claude vocabulary used on this page, explained once.
- Connector
- A link you set once between Claude and an outside service, so Claude can use that service while it answers your questions.
- Tool
- One named job a connector lets Claude do. Claude decides alone when to call it, and the directory sheet lists every tool by name.
- Authorization
- The service's own sign-in screen, where a person grants Claude the access it will use later. It can be taken back the same way.
- Approval
- The confirmation Claude waits for before it does something that changes an account, shown in the chat at the moment it matters.
- MCP
- The common standard every connector is built on: it is what lets an assistant like Claude talk to an outside service such as Booking.com.
Add the Claude Booking.com connector in three steps
- 01
Open the connector list
In Claude's settings, go to Customize, then Connectors, and find Booking.com in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before members can add it.
- 02
Start the connection
Click Connect on the Booking.com row and follow the window that opens. If the link stops working later, choose Disconnect, then connect again: that is the documented way to repair it.
- 03
Read what you are granting
When a service shows an authorization screen, read it before you accept. It belongs to the service, not to Claude, and it is what sets the scope of the access Claude will use afterwards.
The single tool, and what it reads
Booking.com gives Claude 1 tool: 1 that read your account, 0 that change something in it.
Booking.com's connector rests on one tool. Its name stays in English, exactly as Claude shows it, and Booking.com's own developer page describes what it does.
- 1 read
What Claude reads (1)
1 toolOne search tool that looks at Booking.com listings without changing anything.
accommodations_search
Looks for hotels, apartments and other places to stay on Booking.com for a destination, dates and number of guests, then narrows the list by accommodation type, facilities, rating or meal plan. Each result can then be opened on Booking.com for the full details.
What Claude asks before it acts
By default, Claude stops and asks for confirmation before each action it takes on an account for someone, in the conversation, at the moment it matters.
Here the only tool runs a search, so there is little to approve. On Team and Enterprise workspaces, owners decide whether members may let some actions through without a prompt each time, and they can limit what any connector may do for the whole organization; nobody overrides that from their own account. Claude also works with the rights of the person who connected and nothing more. Booking.com adds that it receives only what the search needs, such as destination, dates, guests and filters, and never your chat history.
Which plans it is on
No official source publishes plan availability connector by connector: 0 of the 819 directory sheets shows it, and that gap is real.
The published rule is general. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members connect. For the current state of this one, look at its sheet in the official directory. Note that only Booking.com documents this connector; no Claude help page covers it.
Where the Booking.com connector stops
A connector is not an automation. Claude calls this tool while it answers you, so no search runs by itself and no price alert ever fires.
By default, its sheet exposes only reading, and that is an observed floor rather than a promise: an administrator can open actions no public page shows. The partner badge is not a security audit, and Anthropic writes on every sheet that it neither chooses the tools a publisher exposes nor guarantees they behave as announced. Connect what comes from a publisher you know. For a connector built very differently, with a long list of tools, compare with the Claude activecampaign connector.
Need help connecting Booking.com to Claude?
A person reads every message.