Kiwi.com MCP Server vs Skyscanner Travel 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.

Skyscanner Travel APIs

Thirteen documented search APIs cover flights, hotels and car hire behind one x-api-key header, with default rate limits published per endpoint and no usage fee. Access needs an approved application, an audience above 100,000 monthly users and a commercial agreement, and the usage guidelines bar live-price calls made without a user action. Booking happens on supplier sites.

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

Skyscanner Travel APIs

1. Send the key in the x-api-key header on every call to https://partners.api.skyscanner.net. CORS is not supported, so call from a server
2. Create a live search only when a user has given origin, destination and exact dates. Use the indicative price endpoints for open-ended questions
3. Poll /search/poll/{sessionToken} until status is RESULT_STATUS_COMPLETE, and replace earlier results only when action is RESULT_ACTION_REPLACED
4. Start a new session when a poll returns 400. Flight session tokens last about an hour and hotel sessions at most 15 minutes
5. Pass each deepLink to the traveller unchanged, since altered encoding breaks Impact tracking, and never put personal data in subid2