Connect Vrbo to Claude

Why there is no "Vrbo MCP server"

MCP, the Model Context Protocol, is Anthropic's open standard for wiring AI assistants to outside systems. An MCP server needs an API behind it, and that is where Vrbo differs from every PMS we have covered in this series. Vrbo's API program runs through Integration Central, which exists for property management software companies building official connectivity integrations. Vrbo's own guidance states that Integration Central is not intended for property managers who use software to manage bookings; they are pointed to their account manager or a connectivity provider instead. There is no page in the owner dashboard where you generate an API key for your own account.

That single fact shapes the whole architecture. The API access Vrbo grants goes to the software layer above it, so the practical way to give Claude live access to your Vrbo data is to go through that layer.

Pick your route

What you can ask once the data is in front of Claude

• "Which Vrbo check-ins land in the next 7 days, and are any same-day back-to-backs?"
• "From this reservations export, what's my average length of stay and booking lead time by property?"
• "Compare this month's payout summary to last month's and explain the difference."
• "Find every gap night shorter than 3 days in the next 60 days on this calendar."
• "Which properties have the highest cancellation rate in this export?"

Route 1: connect through your PMS

Vrbo grants API access to connectivity partners, so the PMS layer is where live programmatic access to your Vrbo data actually lives. Escapia is the in-family option, a vacation rental PMS that is itself part of Expedia Group. Independents work the same way: Guesty documents its Vrbo connection, Hostaway holds Vrbo Elite Connectivity Partner status for 2026, and OwnerRez runs an API-integrated Vrbo channel. Once bookings sync into the PMS, connecting Claude is a solved problem: a small read-only MCP server against the PMS API, which is exactly what the rest of this series builds.

Route 2: Vrbo's exports, step by step

I've attached my Vrbo reservations export (CSV) and payout summary.
1. Profile the columns so we agree on what's in here.
2. Occupancy, ADR, average length of stay, and booking lead time by property.
3. Flag anything odd: cancellations clustering on one listing, payout rows
   that don't match a reservation, gap nights under 3 days in the next 60 days.
Show the numbers as tables and tell me which property needs attention first.

What Expedia Group is actually shipping on AI

Worth watching, because Vrbo's parent company has been unusually active on MCP, just not on the host side yet.

• Live now An open-source Expedia MCP server, for travel recommendations. Expedia Group publishes expedia-travel-recommendations-mcp on GitHub: an official MCP server exposing hotel, flight, activity, and car recommendations, keyed by an Expedia API key. Traveler-facing data, not your bookings.
• Live now Vrbo inventory in Expedia's Rapid API. Partners can pull Vrbo properties through Rapid by passing supply_source=vrbo. Rapid is for travel sellers distributing inventory, and it is the clearest sign that programmatic Vrbo access flows through Expedia Group partner infrastructure, not a Vrbo host API.
• Announced May 2026 A B2B MCP server for partner AI agents. Skift reported that Expedia Group is launching an MCP server so business partners' AI agents can access its travel inventory directly, described by B2B chief product and technology officer Karen Bolda as going live "in the coming months."
• Announced June 2026 A Dev MCP server and AI agents in Partner Central. At Explore 2026, Expedia Group introduced a Dev MCP server that helps developers find documentation and test integrations, plus three AI agents for lodging partners (Partner Companion, Content Agent, Autonomous Distribution). Its developer hub says the company is "building MCP capabilities that work seamlessly with our APIs" and calls the work an exploration phase.

The honest read: every MCP move so far points at travelers, distribution partners, and Expedia's own developer experience. None of it gives a host conversational access to their own reservations. If that changes, the first place it likely lands is the software layer, which is one more argument for Route 1.

FAQ