Blog

Travel MCP servers in 2026: who covers air, hotels, and ancillaries

By Loris Mazloum

If you are building an AI travel agent in 2026, the first question is no longer “should we use MCP?” but “which servers already exist, and what is still missing?” Large travel players now expose flights, hotels, and recommendations as Model Context Protocol tools. The layer after the ticket, meaning insurance, eSIM, lounges, fast track, transfers, and entry checks, is much thinner.

This is a builder’s map, not a ranking. Scope and access change quickly, so treat each row as a pointer to the provider’s own docs.

The public travel MCP servers builders mention most

Provider What the server exposes (per public docs or press) Access
Sabre Agentic-ready APIs behind an MCP gateway: flight and hotel search, booking management, fare rules, and ancillary actions such as checked bags Sabre customers
TPConnects Iris Normalised airline fares, ancillaries, rules, and servicing across 60+ airlines (announced April 2026) OTAs, TMCs, travel sellers
lastminute.com Flight MCP Server (January 2026); hotel and dynamic-packaging servers announced as next steps Listed on Anthropic’s marketplace for experimentation
Kiwi.com One remote tool, search-flight, at mcp.kiwi.com Public remote endpoint
Expedia Group Hotel, flight, activity, and car recommendations over stdio or Streamable HTTP Expedia API key
Amadeus Discover Recommended activities and destinations; OAuth2 token, Streamable HTTP Amadeus Discover credentials
Travel Code Corporate travel: flight and hotel search, bookings, orders, flight status (launched August 2026) Hosted at mcp.travel-code.com with OAuth, or self-hosted
MAQAMI Live hotel rates, flight search, places and airports, prebook and book (October 2026) Public remote endpoint at mcp.maqami.co, no API key
eDreams ODIGEO Proprietary MCP network powering flight, hotel, and car search and booking in Amazon’s Alexa+ (October 2026) Partner integration (Alexa+), not a public endpoint
RouteStack.ai Flights, hotels, and cars behind one MCP endpoint, with merchant-of-record, PCI, and payouts handled; activities and vacation rentals added in early Q4 2026 Builder packages; sandbox open
Vibe Corporate travelers search, book, pay for, and manage flights, hotels, and rail in ChatGPT, Claude, and Copilot within TMC policy (July 2026); Navan launched a read-only MCP for travel and spend data the same month Via TMCs using Vibe
Mirai Hotel direct-channel booking engine over MCP: availability and prices, promotions, booking, modification, and cancellation; powers hotel plugins in ChatGPT (October 2026) Mirai hotel clients

Two patterns stand out. Airline-content servers (Sabre, Iris) go deep on the ticket, including air ancillaries like bags. Consumer-brand servers (Kiwi.com, Expedia, Amadeus Discover) lean toward search and recommendations, where the booking often finishes elsewhere. Newer entrants such as MAQAMI, Travel Code, and RouteStack go further and let the agent book, and OTAs are starting to sell through third-party assistants this way: eDreams ODIGEO now books through Alexa+ over its own MCP network. That puts confirmation design squarely on the builder: MAQAMI’s own launch post warns that booking creates a real reservation, so the agent should confirm with the user first.

Where MCP fits next to NDC and plain REST

Sabre has said publicly it sees MCP as the next shift after NDC (Travolution). In practice MCP sits on top of supplier APIs rather than replacing them: the agent discovers tools and their schemas over a standard session, and the server still calls airline, hotel, or ancillary systems underneath.

Not every agent integration is MCP either. Duffel, for example, powers travel inside Meta’s Muse agent through an API connector (Duffel). Choose MCP when your product lives in a chat or IDE host and you want standard tool discovery; REST is still fine for headless back ends. Our MCP vs REST notes go deeper.

The gap: the trip after the ticket

Once a PNR exists, a traveller still asks for things no flight server returns:

Some suppliers already bundle part of this behind one REST schema. Tripgic, for instance, describes eSIM returning in the same JSON format as its lounge and fast-track products (Tripgic), and Zetexa sells eSIM alongside lounge, fast track, and meet-and-greet through one API (PR Newswire via StreetInsider). For an agent, the question is whether those extras show up as tools it can quote, confirm, and issue in-session.

How to assemble a full-trip MCP stack

  1. Pick the ticket source. An airline-content or flights server, or your existing air API.
  2. Add an ancillary shelf. One server or API for the non-ticket jobs above, so the agent does not juggle five supplier contracts.
  3. Enforce quote-then-confirm. Price before the model commits, explicit traveller confirmation on paid calls, and an idempotency key on retries.
  4. Log every paid call. Per-call cost, supplier, and customer tag, so finance and support can trace what the agent did.

Ancilair covers step 2 as a pay-per-call marketplace for AI agents: MCP, REST, and CLI, one token, supplier rates passed through with 0% markup on the hosted marketplace. Setup notes for common hosts live on the agents page, including Claude and Cursor.

Sources

Provider scope summarised from public pages as of October 2026; check each provider’s docs before integrating. Not legal or insurance advice.

Questions

Which travel companies run public MCP servers?
Public examples include Sabre (agentic APIs plus an MCP server), TPConnects (MCP on its Iris airline-content platform), lastminute.com (a Flight MCP Server), Kiwi.com (a remote flight-search server), Expedia Group (an open-source travel recommendations server), Amadeus Discover (activities and destinations), eDreams ODIGEO (an MCP network behind Alexa+ booking), RouteStack (flights, hotels, cars, and soon activities behind one endpoint), Travel Code and Vibe (corporate travel), and MAQAMI (hotel and flight search and booking). Check each provider's docs for current scope and access terms.
Do travel MCP servers cover ancillaries?
Mostly air ancillaries tied to the ticket, such as bags or seats on airline-content servers. Non-ticket extras like travel insurance, eSIM, lounges, security fast track, transfers, and entry-document checks usually need a separate tool layer.
Is MCP replacing NDC?
Sabre has said publicly that it sees MCP as the next distribution shift. MCP does not remove the need for airline or supplier APIs; it standardises how an AI agent discovers and calls them.
Is "travel MCP" the same as Mobile Passport Control?
No. Here MCP means Model Context Protocol, the open standard for giving AI agents tools. Mobile Passport Control is a US CBP airport program.