Travel Gateway

Third-party catalogue

15 travel MCP servers we would put in front of a developer. We point at them and do not host, proxy, or take a cut. Status comes from our own scheduled probe, so a server that stopped working says so.

Servers that scrape a site whose terms forbid it are excluded, however useful they look. Partner-gated servers are listed and labelled, because a developer who already holds that contract wants to know they exist.

all group-travel flights-search flights-booking hotels split-stay rail activities-tours visa-docs disruption-claims ground-ancillaries

Booking.com Demand API unknown official

Booking.com · curated 4.5/5 · auth: partner

The official Booking.com server over their Demand API: accommodation and room search, attractions, car hire and flights. The widest licensed hotel inventory available over MCP, and the only route to it that does not involve scraping.

hotelsactivities-toursground-ancillariesflights-search

3 caveats
  • Partnership agreement required. There is no trial key.
  • Rate limited with HTTP 429; back off rather than retrying tightly.
  • The affiliate ID forms part of the endpoint URL, so it differs per partner.
claude mcp add --transport http booking https://demandapi-mcp.booking.com/v1/mcp/YOUR_AFFILIATE_ID --header "Authorization: Bearer $BOOKING_DEMAND_API_TOKEN"

https://developers.booking.com

Expedia Group partner server unknown official

Expedia Group · curated 3.5/5 · auth: partner

Expedia's partner-facing server, complementing their Rapid API. Their separate consumer connector is aimed at travellers inside a chat client rather than at developers building their own agent.

hotelsflights-searchground-ancillaries

2 caveats
  • Partner agreement required for the B2B server.
  • The consumer connector is not a substitute: it is built for a person chatting, not for your agent's own OAuth.

https://developers.expediagroup.com

Sabre agentic APIs unknown official

Sabre · curated 3.5/5 · auth: partner

Sabre's own server over their agentic APIs: shopping, booking and servicing at GDS scale. Listed because a developer who already has a Sabre contract should know it exists. We do not rebuild what a GDS already does.

flights-searchflights-bookinghotels

3 caveats
  • Enterprise sales cycle, not a signup form.
  • Transport and authentication are not publicly documented; your account team supplies both.
  • This one can actually issue tickets. Keep it well away from an unsupervised agent.

https://www.sabre.com

Travelport TripServices unknown official

Travelport · curated 3.5/5 · auth: partner

Travelport's MCP layer over TripServices, rolling out through agency platforms. The second GDS route worth knowing about, and the one already deployed across several hundred agencies.

flights-searchflights-bookinghotels

2 caveats
  • Not self-serve.
  • Availability depends on your agency platform having enabled it.

https://www.travelport.com

Amadeus self-service (community) unknown community

community · curated 3.0/5 · auth: api_key

Community server over the Amadeus Self-Service APIs. Amadeus publishes no MCP server of their own; their announced developer toolkit is a different thing and was waitlisted at the time of review.

flights-searchhotels

3 caveats
  • Explicitly unaffiliated with Amadeus.
  • Test environment data is cached and incomplete; do not judge coverage from it.
  • Self-service content is thinner than the enterprise Amadeus offering.

https://developers.amadeus.com

Apaleo property management unknown official

Apaleo · curated 3.0/5 · auth: oauth

Vendor server over a cloud hotel PMS. Not for finding a room: this is for operators who run properties on Apaleo and want an agent reading their own reservations and availability.

hotels

2 caveats
  • Alpha. Expect breaking changes.
  • Operator-facing. It answers nothing useful for a traveller shopping for a room.

https://apaleo.com