If you only need to read public Airbnb data, an open-source Airbnb MCP server like openbnb's is free and enough. If you need an AI agent to act on your listings, updating rates, syncing calendars, handling bookings, you need an authorized server that holds real partner access, which is the property-management or channel-manager category. Choose by whether you need to read or to act.
"Airbnb MCP" has quietly become a real search, and almost everything it turns up comes from developers and third parties. There is no official Airbnb MCP server today, so every option you will find is one of two things: a third-party tool that reads Airbnb's public pages, or a property or channel-management server that acts on the account you already run. This post lays out what each can do, where each falls short, and how to pick the right one for your use case.
Key takeaway: The Airbnb MCP options split cleanly by capability. Open-source repos and hosted scrapers read public listing data and little else. Property-management and channel-manager servers hold authorized access and can take actions, from updating a rate to managing a booking, inside the account you control. As of August 2026 no server from Airbnb itself exists, so the practical question is whose access the tool runs on.
Three kinds of tool show up when you search for an Airbnb MCP, and they are built for different jobs.
The first is the do-it-yourself open-source server. The most visible is openbnb's mcp-server-airbnb, which describes itself as "a comprehensive MCP Bundle for searching Airbnb listings with advanced filtering capabilities and detailed property information retrieval" (openbnb). It exposes two tools, airbnb_search and airbnb_listing_details, and it is upfront that it "is not affiliated with Airbnb, Inc." and works on "publicly available Airbnb listings." It even ships an --ignore-robots-txt switch to "bypass robots.txt restrictions when making requests to Airbnb," which tells you how it gets its data.
The second is the packaged scraper. Apify, for instance, offers Airbnb scraper Actors exposed as MCP tools that "scrape Airbnb rentals in your chosen destinations" and extract "descriptions, locations, prices per night, ratings, reviews count, host details, amenities and more" (Apify). It is the same idea as the open-source repo with a hosted service wrapped around it: read public data at scale.
The third is the property- or channel-management server, which runs on the account an operator already holds. Hospitable, which calls itself the first official MCP server from a short-term-rental platform, connects an agent to "properties, reservations, guest communication, calendars, tasks" and covers Airbnb, Vrbo, Booking.com, Agoda and Google Vacation Rentals (Hospitable). On the hotel side, Apaleo turned its "Core API portfolio, 237 endpoints, into MCP tools" (Apaleo), and Guesty has opened a channel so "external AI models and developer applications can seamlessly interact with" its platform (Guesty). You will also see "guesty mcp," "hostaway mcp," "cloudbeds mcp" and "mews mcp" as navigational searches; some are official, some are community wrappers, so check whose name is on the server before you connect it to your account.
The dividing line is read versus act. Reading is a listing's price, availability and reviews. Acting is changing a rate, closing a date, replying to a guest, or moving a booking.
The scraper-style options are read-only by design. Hospitable states the limit plainly: community Airbnb MCP servers are "read-only," so an agent "can look up listings, prices, and availability, but it cannot send a message to your guest, update your calendar, or take any action on your account" (Hospitable). That is fine for research, price comparison, or feeding market data into a model. It is not enough if you want an agent to run any part of your operation.
The authorized servers can act because they sit on access you already have, and that access is also what keeps them reliable: a scraper depends on Airbnb's public pages staying stable and on not being blocked, while a PMS or channel-manager server works through the sanctioned partner connection it already uses to sync your rates. That partner access is the whole reason one option can act and the other cannot; how the API and MCP layers connect is the subject of Airbnb API integration vs an MCP connection, so this post stays on the choice between the tools.
The four options below answer to different owners and do different work. Match the row to what you actually need the agent to do.
| Option | Built for | Read or act | Data source | Channel coverage |
|---|---|---|---|---|
| Open-source server (e.g., openbnb) | Builders, researchers | Read-only | Scrapes Airbnb's public pages | Airbnb only |
| Hosted scraper (e.g., Apify) | Market and price research | Read-only | Scrapes public pages | Airbnb (per scraper) |
| PMS or channel-manager server (e.g., Hospitable, Guesty, Apaleo) | Operators, property managers | Read and act | Authorized account access | Multi-channel |
| Jetstream managed MCP channel manager | Hotels and resorts distributing to STR channels | Read and act; booking behind confirmation | Authorized; official Airbnb API partner integration; two-sided (supply and OTA) | Multi-channel |
The right tool depends on what you do: build software, run a property, or manage a portfolio.
If you are a builder or analyst who needs Airbnb data, for a price tracker, a market study, or a prototype, an open-source server or a hosted scraper is the right and inexpensive starting point. Both read public listings, neither asks for account access, and you can be running in an afternoon.
If you operate one or a few properties and want an agent to actually do things, replying to guests, adjusting rates, managing the calendar, you need an authorized server from your PMS or channel manager. Only an authorized connection can act, and it is the one place a read-only scraper cannot follow you.
If you manage a portfolio or run a hotel moving inventory onto short-term-rental channels, add two more questions. Does the server cover every channel you sell on, or only Airbnb? And does it connect the supply systems you already run, so the agent works from the same rates and availability as the rest of your stack? For a portfolio, the best MCP for short term rentals is the one that handles your whole distribution, with Airbnb as one channel among several.
Jetstream sits in the authorized, read-and-act category, built for hotels and resorts that distribute onto short-term-rental channels. It runs a two-sided MCP server for Airbnb and the other channels you sell on, connecting the CRS or PMS you already operate on one side and your OTA channels on the other, with production connections that include an official Airbnb API partner integration. Because it holds that partner access rather than scraping public pages, an agent can read your rates and availability and, with permission, act on them, with booking behind a confirmation step.
This is a capability comparison. The open-source tools do their read-only job well; they simply cannot act on your account. For the category background, what an MCP channel manager is covers it.
Most of what shows up under "Airbnb MCP" today reads public data and stops there, which is genuinely useful for research and prototypes. Once you want an agent to run part of your business, what matters is whose access the tool runs on. Pick for read or for act, and if you need to act across the channels you actually sell on, choose an authorized, multi-channel server and confirm who keeps it running.
If an Airbnb MCP that can act on your listings is on your roadmap for the next couple of quarters, Jetstream runs the connector, the channel mappings and the authorization scopes as a managed service, with an official Airbnb API partner integration behind it. Book a demo to see it against your own channels.
No. As of August 2026 Airbnb does not publish its own MCP server. Every "Airbnb MCP" you will find is either a third-party tool that reads Airbnb's public pages or a property-management or channel-manager server that acts on the account you already hold. The most visible open-source project even states that it "is not affiliated with Airbnb, Inc."
There is no single best MCP for short term rentals; the right one depends on whether you need to read or to act. For market research or a prototype, an open-source or hosted scraper is enough. For running an operation, where an agent updates rates, syncs calendars, or manages bookings, you need an authorized PMS or channel-manager server that covers every channel you sell on, Airbnb included.
Only an authorized server can, and even then it should ask first. Read-only scrapers cannot take any action on an account. Authorized property-management and channel-manager servers can act, but reputable ones keep booking behind an explicit permission scope and a confirmation step, so the agent does not complete a reservation on its own.
They are safe in the sense that they only read public data and never touch your account. The caution is about how they collect that data: openbnb's server, for example, ships an --ignore-robots-txt option to "bypass robots.txt restrictions when making requests to Airbnb." Scraping public pages against a site's robots directives can run into that site's terms, so use these tools with that in mind and keep account-level work on an authorized connection.
A read-only server exposes only Resources, the data an agent can look at, such as prices, availability and reviews. A read-write server also exposes Tools, the functions an agent can call to change something, like a rate or a calendar. The MCP specification draws this line itself, defining Resources as data sources and Tools as executable functions that perform actions.
In practice, yes, one has to hold that access somewhere. Airbnb grants write access to listings, rates and reservations only through its approved partner program; there is no public self-serve signup for it. An MCP server that can act does so through a partner that already holds that access, which is why authorized PMS and channel-manager servers can take actions and scrapers cannot.