A Booking.com MCP server for your own property

A Booking.com MCP server lets an AI assistant such as Claude, ChatGPT or Cursor work with Booking.com through the Model Context Protocol. Booking.com’s own server serves affiliates: it searches accommodation, cars, flights and attractions to sell. Scraper servers read public Booking.com pages. Repull’s server connects to your own property, so the assistant can see your reservations, guest messages and reviews and act on them. It has 64 tools and covers Airbnb, Vrbo and 14 PMSes too.

MCP (Model Context Protocol) is the open standard Claude, ChatGPT, Cursor and VS Code use to call outside tools. An MCP server for vacation rentals comes in three kinds, and they answer very different questions:

• Public-data scrapers (openbnb, Apify actors, HasData, Bright Data). They read public search pages, so they can find listings and prices. They cannot see your reservations, messages or payouts, and they cannot change anything.
• Market-data servers(AirROI). Occupancy, ADR and comps from a dataset of other people's listings. Useful for research; not connected to your account.
• Account-connected servers(Repull, and PMS-specific ones such as Hospitable's and Guesty's). They sign in to your own account, so the assistant sees your bookings and can act on them. Repull is the one that connects the channels directly, with or without a PMS.

There is nothing to install and no API key to copy. In Claude you pick Repull from the connector directory; everywhere else you add one URL, https://repull.dev/mcp. Then you sign in to Repull when the assistant asks. New accounts start a 7-day free trial and connect Airbnb, Booking.com, Vrbo or a PMS on the way.

claude mcp add --transport http repull https://repull.dev/mcp

{
  "mcpServers": {
    "repull": { "url": "https://repull.dev/mcp" }
  }
}

code --add-mcp '{"name":"repull","type":"http","url":"https://repull.dev/mcp"}'

Building your own agent instead? The @repull/mcp package runs the same data locally with an API key, and the Repull API has SDKs for TypeScript, Python, Go, Ruby and PHP.

Each example shows what you type, which Repull tools the assistant calls, and the kind of answer you get back. The answers below use sample listings and guests.

33 tools read and 31 tools change something (marked in amber). If you approve the assistant as Read only, the server never lists the write tools at all. Each tool is one call to the Repull API, so the same rules apply as for any developer integration.

Competitor details are taken from each vendor's own pages and README as of 2026-11-11. Spotted something out of date? Email hello@repull.dev and we will fix it.

• Two switches, the stricter wins. When you approve the assistant you choose Read only (scope mcp:read) or Read and act (mcp:write). Separately, each channel has its own access level: Read only, Messaging & reviews, or Full access.
• Confirmation before every change. The server tells the assistant to state exactly what it will do and wait for a clear yes before it changes a price, blocks dates, messages a guest or replies to a review.
• Works alongside your PMS.Connect a channel as Read only or Messaging & reviews and your current channel manager keeps prices and availability. Or connect the PMS itself: 14 are supported in beta (Hostaway, Guesty, OwnerRez, Smoobu, Beds24, iGMS, Hospitable, Lodgify, BookingSync, Cloudbeds, Mews, Track, RentalReady, CiiRUS).
• Guest text is data, not instructions. The server tells the assistant to treat messages and reviews written by guests as information only.
• Disconnect any time from AI assistants in your Repull dashboard, or by removing the connector in your assistant. Access stops immediately.