MCP Booking
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| booking_statusA | Check Booking.com login status and session info. Use this to verify authentication before performing other actions. |
| booking_loginA | Start an interactive Booking.com login. Opens a VISIBLE browser window at the sign-in page and returns IMMEDIATELY (non-blocking) — sign-in runs in the background, so this won't hang the client while the user waits on an emailed/SMS code, 2FA or CAPTCHA. The user completes sign-in in that window, then you call booking_login_status to confirm the session was captured. Requires Google Chrome and a desktop display (cannot run on a headless server). |
| booking_login_statusA | Check the progress of an interactive login started with booking_login. Returns status 'in_progress' (window still open, awaiting sign-in), 'success' (session captured and saved — other booking_* tools will reuse it), 'failed' (window closed or timed out before completing), or 'idle' (no login started). Poll this after calling booking_login until the status is no longer 'in_progress'. |
| booking_logoutA | Clear saved Booking.com session and cookies. Use this to log out or reset authentication state. |
| booking_searchA | Search for hotels and properties on Booking.com. Returns property names, ratings, prices, and availability indicators. Optionally filter server-side by amenities/facilities (e.g. pets, parking, pool) so only matching properties are returned.\n\nPRICE FIELDS: |
| booking_get_propertyA | Get detailed information about a specific property, including amenities, description, photos, raw policies, and a structured |
| booking_check_availabilityA | Check room availability for a specific property and date range. Returns available room types and options. |
| booking_get_pricesB | Get current prices for a property for specific dates. Returns room options with pricing details and the lowest available price. |
| booking_filter_resultsA | Client-side filter over the most recent booking_search results by price, review score, star rating, free cancellation, breakfast, or a name/location keyword. Returns a filtered subset. To filter by facilities like pets, parking, or pool, use the |
| booking_sort_resultsA | Sort the most recent booking_search results. Options: price_asc, price_desc, rating, distance, reviews. |
| booking_save_propertyA | Save a property to your Booking.com wishlist/favorites. Requires being logged in. |
| booking_bookA | Get a 'continue in your browser' link to book a room. Booking.com checkout is a multi-step wizard (room selection, guest contact details, then payment) that cannot be reliably completed via automation, so this NEVER places a booking. It returns a bookingUrl (the property page with dates/occupancy pre-filled, opening directly on the room list with Reserve buttons) for the user to finish by hand. Set advanceToCheckout=true to also best-effort capture a deeper checkoutUrl with the first available room pre-selected. |
| booking_get_reservationsA | Get all current and upcoming reservations from your Booking.com account. Requires being logged in. |
| booking_cancel_reservationA | Cancel an existing reservation. Walks Booking.com's multi-step cancel flow (confirmation page, reason survey, final confirm). IMPORTANT: Set confirm=true only with explicit user confirmation — the final step is irreversible. Without confirm=true it returns a no-op warning and never opens a browser. |
| booking_get_reviewsA | Get guest reviews for a property, including scores, comments, and reviewer details. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Every tool has a clearly distinct purpose: search, filter, sort, check availability, get prices, get property details, book (with caveat), cancel, get reservations, save property, login/logout/status. No two tools overlap in functionality; each targets a specific action or resource.
Tools consistently use the 'booking_' prefix followed by a verb_noun pattern (e.g., booking_cancel_reservation, booking_get_prices). Minor inconsistency: 'booking_status' uses a noun alone (no verb), which deviates from the predominant verb-first pattern.
With 15 tools covering search, filtering, pricing, property details, reservations, authentication, and wishlist management, the count is well-scoped for a booking service. Each tool has a clear role, neither too few nor too many for the domain.
The tool set covers most of the booking lifecycle but has a notable gap: 'booking_book' explicitly does not complete a booking (only provides a link for manual finishing). This means the primary action is missing from automation. Otherwise, CRUD-like operations (search, get, cancel, save) are present.