Booking.com MCP server: let your AI agent search hotels with total price and cancellation terms
Wield is an MCP server that gives your AI agent one Booking.com tool. The agent can search hotels and stays by destination and dates. It gets back the total price for the stay, the price before discounts, the review score, star rating, free cancellation deadline and link. The search runs in your own browser with your own session. Your passwords and cookies never leave your computer.
Booking.com Search hotels and stays with total price, rating and cancellation terms
Read-only, no loginRuns in your browser only
Parameters (15)
What your agent gets
A Wield recipe is a small public file that describes the request Booking.com's own search page makes. Your agent runs it through wield-mcp, the local MCP server on your computer.
| Recipe | What it does | Login | Status (7 Nov 2026) |
|---|---|---|---|
booking.com/search-stays | Searches hotels and stays: total price, price before discounts, score, stars, distance, free cancellation and link | No | ok (browser only) |
The recipe takes a destination, check-in and check-out dates, adults, children's ages, rooms and optional filters. The filters cover a budget per night, a minimum review score, stars and free cancellation. Sponsored results are dropped by default. The how-to guide shows example prompts.
How a request flows
- You ask your agent for hotels in Lisbon from 11 to 13 December for two adults, with free cancellation.
- The agent calls
find_recipe, thenrunwithbooking.com/search-stays. wield-mcppasses the run through a local bridge to the Wield extension in your browser.- The extension loads one search page from a booking.com tab, with your own session.
- The results return to your agent. Nothing passes through wield.run.
What leaves your computer
- One search page per call, loaded in your browser.
- Wield never reads, copies or sends your cookies or passwords.
- Results go to your AI app and are marked as website content, so your agent is told not to follow instructions found in them.
- Logs stay on your computer. They never record request bodies or query values.
Recipes are data, not code, and no JavaScript from the registry runs in the page. The registry signs every recipe with Ed25519, and wield-mcp refuses a recipe that is unsigned or has changed. Wield sends no Cookie or Host headers, and it redacts derived tokens from results and logs.
Booking.com terms, in plain words
The recipe's notes say Booking.com's terms prohibit scraping and automated bulk access. This recipe loads one search page per call in your own browser session, the way you would. It never books. Check the site's terms before you automate anything beyond your own searches.
Limits and what is not working yet
- This recipe runs in your browser only. In our check, a plain request from a server got a JavaScript challenge.
- Our live check for Lisbon, 11 to 13 December with two adults, returned 20 results. The page is about 1.6 MB, so runs are heavier than most recipes.
- We have no benchmark row for this recipe yet.
- If Booking.com shows a check, Wield stops and asks you to solve it in your own tab. Wield never tries to solve a check itself.
Every run stops at 12 steps, 40 requests, 5 MB per response or 60 seconds. Pacing is set per site, so a single search cannot run away.
FAQ
Is there an official Booking.com MCP server?
Not that we know of as of 7 November 2026. Wield's recipe reads the same search page the Booking.com website uses.
Which AI apps work with it?
Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. Claude Desktop also has a one-click bundle on wield.run/install.
Does it need a Booking.com login?
No. The search needs no login. It uses the session your browser already has, and your password never leaves your computer.
How does it compare with a browser agent?
We have not benchmarked this recipe yet, so we do not publish a speed or success comparison for it.