About Booking.com MCP server

Learn with these guides how you can connect to the Booking.com MCP server using your affiliate ID and Demand API key.

The Booking.com MCP server is a hosted service that gives your application access to travel search tools through the Model Context Protocol (MCP).

• Partners can use the MCP server via a dedicated endpoint that provides authenticated access to the MCP tools and other capabilities enabled for your account.
• Your application acts as the client: it connects to Booking.com, discovers the tools available to your account, and calls them.
• You do not need to build or host an MCP server.

Use the server to add travel search capabilities to an existing MCP-compatible application or to a custom client built with a MCP SDK.

• An assistant powered by a large language model (LLM) can translate a traveller's request into tool calls.
• A custom client can process the returned data directly and use it in its own travel experience.

• Dynamic tool discovery - tools/list returns the tools and input schemas available to your affiliate account. Use this response as the source of truth for the tools and arguments available to your application.

• Structured results – Tools may return machine-readable data in structuredContent when an output schema is available. Use the published schema to process the structured output, and handle text or other content blocks when structured output is not available.

  See response handling for tool errors and content-only results.

• Destination handling - For any travel service search, the server resolves location names such as cities, hotels, landmarks, or airports before searching. Flight search uses IATA airport or city codes.

• Stateless transport - Requests do not require a persistent server-side MCP session.

• Current inventory – Search tools retrieve current availability, pricing and travel-service information from Booking.com. Availability and prices may change after a response is returned.

The Booking.com MCP server is for approved partners that want to add Booking.com travel search capabilities to an MCP-compatible application or custom client.

Access and available capabilities are configured per affiliate account during onboarding.

Applications can use these tools to build:

• AI travel assistants - Build assistants that understand traveller intent and recommend travel options based on natural language queries.

• Conversational travel assistants - Create chat-based interfaces where travellers can search for and compare travel services using natural language, such as "Find me a pet-friendly hotel in Barcelona under €150."

• Voice-activated search interfaces - Develop hands-free travel search for smart speakers, in-car assistants, or mobile voice apps.

• Multi-modal travel applications - Combine text, voice, and visual search in a single travel experience.

• LLM-driven search wrappers - Use the MCP server within custom search functions or agent-based pipelines.

These use cases can be combined. For example, an application can accept voice input and display the returned search results in a chat interface.

The tools available depend on your affiliate configuration.

• accommodations_search is one example of a tool that may be available to your account. Other search tools may also be enabled.
• Use tools/list as the authoritative source for the tools available to your application.

If enabled for your account, accommodations_search provides access to Booking.com's accommodation data. Use its live schema to check supported parameters and output fields.

Capabilities may include:

• Flexible destination search – Search using location names for cities, regions, landmarks, districts, airport codes and properties. Examples include “Manhattan”, “Big Ben”, “JFK” and “Grand Hotel Vienna”.
• Date and guest handling - Specify check-in and check-out dates, guest occupancy and the number of rooms, including multi-room searches.
• Advanced filtering - Filter results using criteria such as price range, property type, facilities and rating, where supported by the tool schema.
• Content and metadata - Retrieve property information, pricing and other metadata returned by the tool's output schema.

Before getting started, ensure that you meet the following prerequisites:

1. Work with your Account Manager to complete onboarding for your AI use case.
2. Obtain or confirm your affiliate ID and Demand API key with your Account Manager during onboarding.
3. Configure your client using the Get started, or follow the implementation guide to build a custom integration.

Send both credentials with every MCP request:

• Affiliate ID - Your account identifier, sent in x-booking-affiliate-id.
• Demand API key - Your authentication credential, sent unchanged in x-booking-authorization. Do not add a Bearer prefix.

✅ Confirm endpoint access with your Account Manager during onboarding, and use the dedicated endpoint and headers described in these guides.

✅ Keep your Demand API key private. Do not commit it to version control or include it in screenshots, logs or support messages.

Choose Get started to configure an existing client, or the implementation guide to build a custom integration.

Get started

Choose an MCP client and configure its connection to Booking.com.

Get started

Implementation guide

Connect your application, discover available tools, and make authenticated MCP requests.

Read now