Kiwi.com MCP Server vs Travelport TripServices APIs

Kiwi.com MCP Server

A keyless flight search with one typed, read-only tool, 47 filters and a booking link on every itinerary. It can't book, hold, change or cancel, and it has no published rate limits, changelog, terms or version. Each search returns 15 itineraries with no way to ask for fewer.

Travelport TripServices APIs

Public OpenAPI 3.0 files, Markdown docs and an llms.txt cover search, pricing, booking, ticketing, exchanges and hotel stays, with dated release notes through August 2026. Production needs a sales contract and certification with 15 days' notice. No price, API rate limit, status page or SLA is published, and the terms bar automated tools without written permission.

Kiwi.com MCP Server

1. POST to https://mcp.kiwi.com itself. /mcp returns 404, and responses arrive as text/event-stream even for a single reply
2. Send dates as dd/mm/yyyy and set currency, which defaults to EUR
3. Check the error field of every result. A rejected input returns resultsCount 0 with isError false
4. Narrow with price_to, max_sector_stopovers and sort. There is no limit parameter and each search returns 15 itineraries
5. Give the user bookingUrl to book. Don't call feedback-to-devs with user data, because it sends free text to Kiwi.com

Travelport TripServices APIs

1. Request one token and cache it for 24 hours. Travelport declines certification for refreshing more often than every 23 hours without a stated reason
2. Send Accept-Encoding: gzip, deflate and XAUTH_TRAVELPORT_ACCESSGROUP (or TVP-PCC-CORE) on every call. Production traffic without compression is refused
3. Send offersPerPage on a journey-based search, or later calls can't reference its results. Cached searches last 12 minutes for GDS content and 34 for NDC
4. Commit a workbench within 30 minutes or it expires, and read Result/Error in the body even on HTTP 200
5. Get written authorisation for agent access before production. The terms bar automated tools and speculative or duplicate bookings