What Sabre reported
On September 21, 2026, Sabre marked one year of its MCP server. Nearly 80 customers are piloting it or running it in production; Virgin Australia, Flight Centre and the Internova group are named. The figure comes from Sabre itself. How many of them are still in pilot and how many are live is not stated in the release.
Technically the server is a translation layer. AI agents query flight and hotel inventory live instead of guessing. Sabre itself calls it a “universal translator”. According to Sabre, post-booking work is in production too: rebooking, changes, payments, at Internova for example. At Virgin Australia the technology sits behind a conversational flight search that won an industry award in August.
Checking availability live instead of estimating it saves an adviser real time. This is solid infrastructure, and it works where it is deployed.
Who sits at the access point
The named customers are an airline, a global agency group and a US group with several travel brands. All three sell standardizable building blocks: flights, hotels, rebookings. That is the world a distribution system of this kind was built for.
None of the named customers is an owner-managed specialty tour operator in the DACH market. That is not a criticism of Sabre. It describes what the server is for.
What the first production claim reveals
It is telling where Sabre documents production use: in work after the booking. Rebooking, changing, paying. Not in selling. That is plausible, because this is routine with clear rules, and routine is the first thing to hand over.
The same pattern holds for a specialty operator, just at a different point. The routine sits in the enquiry, in the follow-up to the supplier and in the costing. Whoever hands over there first gains advisory time. Whoever hands over only the inventory lookup gains it on the cheapest part of the trip.
What a specialty trip is made of
A 14-day round trip off the main routes consists largely of items no agent finds in an inventory. A local guide who knows the village. A camp with eight beds. A driver who judges the state of the track. A permit that needs weeks of lead time.
The flight and some of the hotels can be queried. The rest is relationship knowledge. And that decides whether the trip works and how high the margin is.
The agent checks the flight in seconds. Afterwards the adviser still waits for the partner on the ground to reply, adds up the line items and writes the offer. The visible time saving arises at the point that cost the least time to begin with.
“An agent that checks flights has not built a trip yet.”
The arithmetic behind it
Two things change the arithmetic here.
First, access becomes the standard. Sabre itself compares MCP with NDC: the industry spent the past decade on NDC and may spend the next one on MCP. What applies to everyone differentiates no one.
Second, the margin of a specialty trip does not arise from retrieving a price. It arises in the composition: which building blocks, in which order, with which markup, for which customer.
A chain follows. If access is open to all, what matters is not who has it but who arranges the blocks into an offer. If the arrangement is the valuable part, the operator needs it as its own process and not as a by-product of a tool. So the path from enquiry to a costed offer has to run end to end. Speeding up single steps is not enough.
Three questions for every integration
For any operator with technology offers on the table right now, a sober test is worth running:
- What share of my trips consists of building blocks that sit in an inventory at all?
- Who calculates the margin while the agent composes, and with whose markups?
- Where does the customer relationship live when the enquiry arrives through someone else's assistant?
Anyone who answers the first question honestly sees quickly how far plain access carries. For flights and package components, very far. For trips that live on relationship knowledge, only as far as the door.
The second and third questions are the less comfortable ones. A margin that someone else's system helps calculate is no longer entirely your own. And a customer relationship that runs through someone else's assistant only belongs to the operator again once the enquiry lands with them. That is exactly why what happens between enquiry and offer matters.
Where Voyager comes in
Voyager builds exactly this path. Productively usable today are the enquiry flow, itinerary composition with price calculation and margin calculation, as well as customer management and a multi-tenant white-label foundation. Supplier integration and automated customer communication are the next expansion stages, and they build on this path.
For this architecture, access like Sabre's is a building block underneath, not a counter-model on top. For the 800 owner-managed specialty tour operators in the DACH market that means: connecting to inventories gets cheaper and more widely available. The ordered path from customer wish to costed offer remains what sets one house apart from another.