This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
bookdata is a small local bridge to the hosted HasData Booking MCP server, which returns Booking.com data as JSON. Give it a destination keyword plus check-in and check-out dates and a party — rooms, adults, children — and it searches the stays available there; give it one property's Booking.com URL for the same dates, and it fetches that property's full details: identity and address, policies, price, rating and reviews, photos, and the room suites available for the window.
The bridge keeps no stay data of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. The captured surface is read-only: it searches and reads public Booking.com listing pages. Despite the vendor name, there is no booking, reservation, messaging, or payment tool in it.
hasdata_booking_search_getBookingSearchResults —
search accommodations by destination. Required:
keyword, checkInDate, checkOutDate, rooms,
adults, children. Optional filters include
childrenAges, sort, price range, bedrooms and
bathrooms, property type, star rating, review score,
facilities and accessibility features, bed and
reservation preferences, language, currency, and
page (25 results per page). Returns each hotel's
id, title and URL, location, policies, price, rating,
review summary, and main photo.
hasdata_booking_place_getBookingPlaceDetails —
fetch one property's full details. Required: url
(a Booking.com property URL), checkInDate,
checkOutDate, rooms, adults, children.
Optional: childrenAges, language, currency.
Returns property identity, address and coordinates,
policies, price, rating and review summary, photos,
and available room suites.
Related MCP server: Airbnb Search & Listings
HASDATA_BOOKING_MCP_URL (optional) — override the
upstream endpoint. Defaults to
https://mcp.hasdata.com/mcp?apis=booking. (The
override hook is this rebuild's own labelled
reconstruction.)
HASDATA_API_KEY (optional) — when set, every
upstream request carries an x-api-key: <key>
header, for the caller's own HasData API key. When
it is not set, no key header is sent. (The header
name and the env name are pinned by the original's
registry record; forwarding the key from this env
var is a labelled reconstruction — the original
surface was captured keyless.)
On the first tool call the client opens a streamable
HTTP session with the upstream: a JSON-RPC
initialize request (protocolVersion 2025-03-26,
clientInfo name bookdata), then a
notifications/initialized notification, then the
tools/call request carrying the caller's arguments
unchanged. When the upstream answers initialize
with an Mcp-Session-Id header, that value rides on
every later request of the session, which is reused
for the life of the process. Replies may arrive as
plain JSON or as server-sent events; both are read.
Successful upstream results pass through verbatim,
including any isError flag the upstream sets.
Failures — a JSON-RPC error, a non-2xx status, an
unreadable response, or a request that cannot be
completed — come back as an isError result whose
text starts with bookdata error: (this rendering
is this rebuild's own labelled reconstruction).
Each tool is also a subcommand taking one JSON argument string:
npx @reneturcios/bookdata hasdata_booking_search_getBookingSearchResults '{"keyword":"Paris","checkInDate":"2026-11-10","checkOutDate":"2026-11-14","rooms":1,"adults":2,"children":0}'
npx @reneturcios/bookdata hasdata_booking_place_getBookingPlaceDetails '{"url":"https://www.booking.com/hotel/fr/example.html","checkInDate":"2026-11-10","checkOutDate":"2026-11-14","rooms":1,"adults":2,"children":0}'
npx @reneturcios/bookdata --versionExit codes: 0 on success, 1 on an isError
result, 2 on a usage error.
npx -y @reneturcios/bookdata mcpMCP client config:
{
"mcpServers": {
"bookdata": {
"command": "npx",
"args": ["-y", "@reneturcios/bookdata", "mcp"]
}
}
}docker run -i ghcr.io/cloudcorprecords/bookdata
docker run --rm ghcr.io/cloudcorprecords/bookdata --versionThe container's default command is mcp, so the first
form is a stdio MCP server; any other arguments reach
the CLI normally.
npm install
npm run build
npm test
npm run devThe test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.
MIT — see LICENSE.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Booking.com stays by destination and dates, and full property details, as structured JSON.
Airbnb stays by location and dates, and full listing details, as structured JSON.
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. Add https://hotels.flightpowers.com/mcp , click Sign in, sign in with Google, and paste your RapidAPI key once on the page that opens. Scripts and clients without a sign-in button send the key as x-rapidapi-key on the same URL.
Google Hotels search: rates, ratings, amenities and what each booking site charges, as JSON.
