UCP. MCP. Gemini. You Already Know How This Ends. You Have No Excuse This Time.

Twenty-five years ago, OTAs arrived with a compelling offer. Expedia and Booking.com would put hotels in front of travelers who would never have found them otherwise. More visibility. More bookings. Hotels signed up.

Nobody read the fine print. Or nobody wanted to.

The fine print said: the guest belongs to us, not you. The data belongs to us. The relationship belongs to us. And every booking you receive through our platform will cost you 15 to 25 percent. Forever. With no escape.

That was the deal. The hotel industry took it because it solved a short-term problem. It created a long-term structural dependency the industry has been trying to escape ever since, largely failing.


Now Google is making the same offer.

The Universal Commerce Protocol (UCP) and Model Context Protocol (MCP) are designed to let AI systems like Gemini move from recommendation to transaction. Google has confirmed UCP is expanding into hotel booking. The pitch is seductive: bypass Expedia. Bypass Booking.com. Let travelers book directly through Google AI.

Hotels are calling this liberation. It is substitution.


What Google has not published for hotel bookings is the part that matters most: the economic model, the data terms, and the rules governing the guest relationship once the booking happens inside Google’s AI surfaces.

OTAs didn’t lead with their commission structure either. They led with the distribution promise. The economics came later, once dependency was established and escape was impossible.

This is the same sentence the industry heard in 1999. Different company. Same structure.


There is a second problem the MCP and UCP conversation ignores entirely.

Transaction infrastructure is useless without visibility infrastructure. MCP and UCP handle connection and checkout. Neither controls whether Gemini recommends the hotel in the first place.

That decision happens earlier, at the layer where AI systems form their understanding of what a hotel is, what category it belongs to, and whether it belongs in a traveler’s consideration set at all. This is the knowledge formation layer. If Gemini does not understand the hotel correctly at that layer, perfect connectivity downstream changes nothing. No inclusion. No recommendation. No booking.

Hotels investing in AI-native booking infrastructure without addressing AI formation layer visibility are building transaction capability on top of an invisible foundation. The booking system is ready. The hotel is not in the consideration set. Nothing gets booked.


The industry spent twenty-five years trying to undo a mistake born of ignorance. Today, it is repeating the mistake with full knowledge.

The only structural exit from intermediary dependency, whether the intermediary is Expedia, Booking.com, or Google, is owning the guest relationship before any intermediary introduces it. Not optimizing within the intermediary’s system. Not connecting more efficiently to the intermediary’s transaction layer. Owning the relationship upstream of it.

MCP and UCP are not that. They are a faster lane into the same dependency structure with a different landlord.


This is Groundhog Day all over again. Same alarm. Same morning. Same mistake. Twenty-five years ago the industry didn’t know how the story ended. Now it does. It just keeps hitting snooze.

The rubber glove is on. The Vaseline is ready. The only question is whether anyone in this industry decides to own their guests before Google does it for them and sends them the bill.

Close