I run Nowistay, a PMS and channel manager for vacation rentals, and the question I get most from hosts this autumn is short: "Can I plug ChatGPT or Claude into my Airbnb account?"
Not directly. As of November 2026, Airbnb offers no official MCP server, no ChatGPT app and no Claude connector, and its API is reserved for approved software partners. Here is what that means if you build or use MCP servers, and the route that does work.
Airbnb's API is partner-only
The Airbnb API documentation covers listings, availability and reservations, but the guides open only after a Partner Portal sign-in and there is no sign-up for individual hosts. Access goes to software companies Airbnb approves as connectivity partners: property management systems (PMS) and channel managers.
So any tool that promises to "connect your AI to your Airbnb account" gets its data one of two ways: through an official partner connection, or through scraping.
What the "Airbnb MCP" servers on GitHub actually do
Search "Airbnb MCP" in any MCP directory and the top results are open-source servers with two tools:
- search listings by location, dates, guests and price
- get listing details for one listing: description, amenities, house rules
They load Airbnb's public pages and extract the content. That makes them search tools for travellers. They never sign in to a host account, so they cannot see reservations, guest messages, payouts or calendar blocks, and they cannot change a price or reply to a guest. They also break whenever Airbnb changes its markup.
Some unofficial libraries go further and call the private API of Airbnb's mobile app with the host's login. Anyone can wrap those in an MCP server. That is the risky version: you hand your Airbnb credentials to a tool Airbnb never approved.
The terms problem
Airbnb's Terms of Service (updated 5 February 2026) say in section 11.1: "Do not use bots, crawlers, scrapers, or other automated means to access or collect data or other content from or otherwise interact with the Airbnb Platform." The same terms let Airbnb suspend or close accounts that breach them.
For a host, that account holds the listings, the reviews and every future booking. Running a scraper from it, or giving its login to an unofficial MCP server, puts all of that at risk for a feature you can get legitimately.
The route that works: an MCP server on top of the PMS
A partner PMS already syncs listings, calendars, rates, reservations and guest messages with Airbnb through the connection the host authorised. Publishing an MCP server on top of that data is the clean path:
- The host asks ChatGPT or Claude a question.
- The assistant calls the PMS's MCP server with the scopes the host approved through OAuth.
- The PMS answers from the data it already holds, and pushes any confirmed change (a price, a blocked date) back to Airbnb through its partner connection.
No scraping, and the Airbnb password never leaves Airbnb.
One limit worth knowing: reservations received from Airbnb are controlled by Airbnb. A connected assistant can read them and message the guest, but alterations and cancellations still go through Airbnb's own flow.
What hosts actually ask once connected
These are real prompt patterns from hosts using our connector:
- "Who checks in this week across all my apartments?"
- "Show my prices for the next 30 days and flag the empty weekends."
- "Set a 3-night minimum stay for July and August."
- "Summarise the conversation with tonight's guest and draft a reply about late check-out."
- "Create a cleaning task for Saturday at 11 am."
- "Give me revenue and cleaning costs per property for Q3, as a table."
The interesting part is that none of these need a new UI. The assistant becomes the interface, and the PMS stays the system of record.
Design rules for write tools in a hosting MCP server
If you build MCP servers for a domain where a wrong write costs money (prices, bookings, guest messages), these are the rules we settled on, and the ones I would look for as a user:
- OAuth, never passwords. The assistant gets a scoped token from the vendor's own login page and the user can revoke it any time.
- Preview, then confirm. Every write is staged first: the assistant shows exactly what will change, and nothing happens until the user confirms. Read-only questions never change data.
- Keep platform-owned objects read-only. Reservations that belong to Airbnb or Booking.com stay read-only on the PMS side.
- Minimise personal data. Guest emails and phone numbers stay hidden unless the user explicitly asks for them.
- Tell users to keep write tools on "ask before acting". Both ChatGPT and Claude let users set per-tool permissions; "always allow" on a pricing tool is a bad idea.
Try it
Nowistay is available as an official ChatGPT plugin and in the Claude connector directory, and the Claude plugin bundle (skills plus the connector config) is open source at github.com/Nowistay/claude. Setup steps are in how to connect ChatGPT or Claude to Nowistay.
Disclosure: I'm the founder of Nowistay. This post is adapted from the original on nowistay.com.
Top comments (0)