Booking.com Hotels MCP — Hotel Search, Hotel Prices & Availability
**Real-time Booking.com rates for agents.** Three things people do with this server. Scan for rate gaps: price_as_seen_from prices the same room from another market, so an agent can sample a property across countries and compare. Put live search in your app: search a destination or look a property up by name, no internal IDs, room-level rates as flat JSON. Run a 24/7 AI travel agent: add the server, sign in with Google, and schedule it. No ads, no sponsored content. You bring your own RapidAPI key, so every search is billed to your plan and never to anyone else's. ### Connecting One URL, whichever way you connect: ``` https://hotels.flightpowers.com/mcp ``` Add it, click **Sign in**, sign in with Google, and paste your RapidAPI key once on the page that opens. It is encrypted before it is stored, only the last four characters are ever shown again, and Disconnect deletes it. Scripts, CI and clients without a sign-in button send the key on that same URL, either as an `x-rapidapi-key` header or as `?rapidapi_key=`. There is no second endpoint to choose between. Either way the key is yours, so every search is billed to your plan and never to anyone else's. Get a key on the Booking Live API listing: https://rapidapi.com/mtnrabi/api/booking-live-api . BASIC is free with 10 requests a month. ### Tools | Tool | What it does | | --- | --- | | `search_hotels` | Live properties and nightly prices for a destination and date range — or a whole stretch of dates in one call via `checkin_date_from`/`checkin_date_to`/`nights` | | `find_hotel_by_name` | One named property — no internal hotel ID needed, resolution is done for you | | `compare_hotel_rates` | Prices one stay across every source you have a key for — Booking.com today, more providers as they ship | All three are annotated **read-only**. They search and read; they cannot book, hold, pay for or cancel anything. ### What you get that other hotel tools don't return - **Price as seen from another country** (`price_as_seen_from`, the API's `proxy_country`) — prices the same stay through a residential connection in the country you name. This is what makes **rate-parity and geo-pricing monitoring** possible, and it is the reason a revenue manager would build on this rather than a generic scraper. *Honest sizing:* the gaps are real but modest and property-dependent. In our own repeat-sampled test one country ran a few percent under another on every property we checked, while a third was not stable enough to read from a single call. Treat it as monitoring you run on a schedule against a fixed property, not a one-shot arbitrage trick. - **Search a property by the name a person would type.** `find_hotel_by_name` resolves it for you; most hotel APIs make you look up an internal property ID first. - **24 Booking.com filters** — free cancellation, meal plans, review score, star rating, facilities, pets, adults-only. Validated *before* the request, so a typo costs you nothing instead of silently returning unfiltered results. - Price, review score and count, room type, location, image and a booking link. ### You always know what a search cost Every response carries `api_usage`, read from RapidAPI's own rate-limit headers: | Field | Meaning | | --- | --- | | `requests_used_by_this_call` | Billed requests this single call consumed | | `plan_requests_remaining` | What is left on your plan right now | | `plan_requests_limit` | Your plan's ceiling | ### Sample response ```json { "results": [{ "name": "Hotel Leone", "price_string": "US$273", "price": 273, "review_score": 8.2, "review_count": 701, "room_type": "Superior Double or Twin Room", "link": "https://www.booking.com/hotel/it/leone.html" }], "result_count": 25, "api_usage": { "requests_used_by_this_call": 1, "plan_requests_remaining": 19994 } } ``` ### Built for - **Rate-parity monitoring** — is your direct rate actually undercut in another market? - **Competitive-set tracking** — watch a named comp set on a schedule - **Travel agents** — availabili
First seen 2 Oct 2026. Evidence as of 2 Oct 2026.
Tools
No tool list captured yet.
Change history
No changes since the first observation. The first snapshot is the baseline.
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Smithery | mrabi/booking | 2 Oct 2026 | 2 Oct 2026 | 1 |