SuperAPI AI Directory

booking-mcp

Search Booking.com stays by destination and dates, and read full property details (rooms, rates, facilities, review scores) as JSON.

Open website

About this tool

Purpose

Booking.com MCP Server is a hosted Model Context Protocol (MCP) server that enables AI clients (such as Claude, Cursor, Windsurf, etc.) to access Booking.com's public accommodation data through tool calls. It provides two read-only tools: search for accommodations by destination and dates, and read the full details of a single property. All data is returned as structured JSON, with no need for users to host the server themselves.

The server reads public property pages visible to logged-out visitors on Booking.com. It does not provide booking, payment, partner commission, or account data functionality.

Main capabilities

The server exposes two tools:

  1. Search accommodations (hasdata_booking_search_getBookingSearchResults): returns one page of accommodation results by destination and dates. It supports rich filters, including distance, meals, accessibility features, bed type preferences, and traveler groups. It returns searchInformation, a results array, and pagination information (page, totalResults, totalPages). Each result includes hotelId, title, url, the room and bed types offered, a location object, a policies object, a price object, star rating, a reviews object (including score, count, and text labels), and photo.

  2. Property details (hasdata_booking_place_getBookingPlaceDetails): returns complete information for a single property based on the property URL and stay window. It returns data organized by section, including overview (id, title, propertyType, structured address, description, highlights, most popular amenities, and photos), bookingDetails (the window and currency corresponding to the price), a rooms array (available suites and their names, bed types, amenities, and pricing variants), a facilities list, houseRules, a ratings array (category ratings), reviews, and questionsAndAnswers.

The server also exposes 16 resources, each corresponding to a parameter whose acceptable values are a fixed list. Reading resources does notconsume credits, and the list can be obtained without an API key.

How to use

Using it requires an MCP client and a HasData API key (which can be created for free in the HasData dashboard, with no credit card required). This is a remote server, and the simplest way to connect is to use the URL and the x-api-key request header, with no need to run a container.

The server URL is the same for all clients:https://mcp.hasdata.com/mcp?apis=booking

OAuth-capable clients can add this URL as a connector and sign in, without placing a key in a config file. In Claude: Settings → Connectors → Add custom connector → paste the above URL and sign in.

For the config-file approach, Claude Desktop only loads local (stdio) servers, so a remote server needs to be reached through a stdio launcher. The @hasdata/booking-mcp package (npm) is that launcher, and it reads the key from an environment variable. The PyPI package hasdata-booking-mcp can also be used, run via uvx without manual installation.

Cursor uses ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (a single project). Windsurf uses ~/.codeium/windsurf/mcp_config.json, with the field name serverUrl rather than url. VS Code uses .vscode/mcp.json in the workspace.

Usage is by entering prompts rather than code, and the agent selects tools automatically. Each successful call costs 10 credits. Example prompts include: search for hotels in Paris from September 15 to 18 for two adults and give the ten highest rated; get the full details of the top result; find four-star hotels near central Paris with free cancellation; compare the cheapest accommodation in Paris and Rome for the same dates.

Note: the listing details tool requires the same dates and guest count as the search, because availability, room types, and prices all depend on the stay window.

When to use it

  • Let an AI agent search and compare accommodation prices and ratings across destinations
  • Get the full amenities, room types, policies, and category ratings of a single listing
  • Combine Booking.com data with other HasData APIs (such as Airbnb) by passing a list via the apis parameter, for example ?apis=booking,airbnb
  • Low-frequency automated agents that can use the free tier long-term

Limitations

  • Read-only public data; no booking, payment, partner commission, or account data
  • The listing details tool must be passed the same dates and guest count as the search
  • Each successful tool call costs 10 credits, regardless of response size
  • The free tier is 1,000 credits per month (about 100 calls), with a concurrency limit of 1 request; paid plans start at $59 per month (200,000 credits, about 20,000 calls), with concurrency increasing with the plan
  • Non-200 responses are not billed, but successful calls with no results are still billed
  • Error handling: the MCP layer usually returns 200 and puts failure information in the result (isError is true); a wrong key shows up as tool output rather than a connection failure; a missing key causes the connection itself to fail with 401; parameters that do not match the schema are rejected before scraping; a search with no availability returns an empty results array rather than an error; an invalid listing URL returns 400
  • This server is not affiliated with, endorsed by, or sponsored by Booking.com
  • Platform terms may restrict automated access, and users are responsible for their own compliance; if collected data includes personal information, you must ensure compliance with regulations such as GDPR and CCPA

Pricing and free tier

The free tier is 1,000 credits per month, no credit card required, roughly 100 Booking.com calls, renewed with the billing cycle. Paid plans start at $59 per month, including 200,000 credits (about 20,000 calls), with the unit price decreasing as usage rises. See the pricing page for current prices.

Other information

This repository is the configuration and documentation for the remote server, with no build step and no containerization needed. The test suite asserts the tool contract, including that ?apis=booking returns exactly two tools, that each tool still declares the required parameters, that the names are unchanged, and that the key is accepted. The last check actually calls the tools and consumes 10 credits. Tests run in CI on every push and on a weekly schedule. The license is MIT.