Head to head · Flight search · October 2026 research run
Kiwi.com MCP Server vs LetsFG
LetsFG scores 66.5 (B) on agent readiness against Kiwi.com MCP Server's 43.4 (E), and leads in 6 of 7 scored categories. Both do flight search.
Best travel search and booking APIs for AI agents · All 120 travel comparisons
Which one, for what
Best for An assistant that looks up fares and hands the user a link to book on kiwi.com, with no setup.
Also in its favour
- No key needed to call it
- No incidents deducted, where LetsFG loses 7 points for them
Watch for
Search only. Booking, payment, changes and cancellations happen on kiwi.com through the link in each result
LetsFG B
Best for A personal agent that wants to search widely and book with the traveller's own card, starting in a free sandbox.
Ahead on
- Reliability, 55 against 45
- Schema & documentation, 83 against 12
- Agent ergonomics, 83 against 35
- Security & auth, 66 against 54
- Maintenance & community, 88 against 13
Also in its favour
- Runs on your own machine
- Free to start without a card
- Open source
Watch for
Tickets are bought by a LetsFG booking agent after the hold, 4 to 11 minutes per the docs, and bookings can pause with questions
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community LetsFG +75
Kiwi.com MCP Server 13
Kiwi.com's 15 October 2026 post says it brought the server in-house in June 2026. Dated to its month, that is 4 to 5 months ago (10 of 30). The 15 October post itself announces platform listings and usage figures, not a change to the server. No releases or changelog entries in the 90 days from 6 August (0). Per the 8 October check, not re-read on 4 November, both issues on the public README repository, opened 3 February and 9 September 2026, had no reply (3 of 15). The official MCP registry wasn't read (its search is a JSON API this run doesn't use) and nothing published shows an entry (0). No package, dependencies or CI to read (0). 10 + 0 + 3 + 0 + 0 = 13.
LetsFG 88
Last release letsfg 2026.5.105 on PyPI, tagged 17 October 2026 with a CLI change for declined cards, by the repository's tags; commits to 25 October (30). In the 90 days from 4 August, tags v2026.5.88 (4 August), v2026.5.101 (14 September), v2026.5.102 and v2026.5.103 (2 October), and v2026.5.105 (17 October), with letsfg-mcp 2026.5.77 and 2026.5.78 on npm in the same release commits (20). Outside pull requests merged on 2 October (#220, a Bearer-lane round-trip fix) and 21 October (#234), and fixes on 2 October cite #221 and #223. Open issue counts and reply times unread, as GitHub's pages answer 403 in our session (15 of 25). In the official MCP registry as io.github.LetsFG/letsfg, a GitHub-verified namespace, latest 2026.5.77 (14 September) while server.json in the repository says 2026.5.79 (15). CI on push and pull request for both TypeScript packages and the Python SDK, Actions pinned to SHAs, Dependabot for actions. We didn't confirm the branch is green (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.
Schema & documentation LetsFG +71
Kiwi.com MCP Server 12
No published tool schema. The 8 October contract, description and typed-input readings came from requests to the server itself and are struck (0). No llms.txt or Markdown docs beyond the README (0). The README and the August 2025 post describe one tool, search-flight, its purpose and its inputs in prose (trip type, origin and destination by city or airport, dates, up to 3 days of flexibility, passengers, cabin class), with nothing on when not to call it (8 of 20). No typed inputs published (0). Two example prompts in the README, no documented error responses (4 of 15). No changelog and no published version (0). 0 + 0 + 8 + 0 + 4 + 0 = 12.
LetsFG 83
OpenAPI 3.1 document served at /developers/api/openapi.json, 36 paths on 2 November (openapi.yaml in the repository still has 16) (25). llms.txt at letsfg.co/llms.txt (last updated 21 October) plus Markdown docs, AGENTS.md and SKILL.md in the repository (10). MCP descriptions say when to call a tool and when not to ("do not retry, give the user the booking_url"), but two contradict the docs and terms on cost and limits, see the negative note (14 of 20). Typed inputs with required lists, enums for cabin class and a nested passenger schema; dates are plain strings (12 of 15). An errors page maps every status and code to an action, and the sandbox documents each failure it can simulate (15). CalVer package versions and git tags, and retirements dated in the docs, but no changelog file (7 of 15). 25 + 10 + 14 + 12 + 15 + 7 = 83.
Agent ergonomics LetsFG +48
Kiwi.com MCP Server 35
The README names one tool. Its definition's size isn't published, and the 8 October measurement came from a struck request, so the earlier partial is kept (20 of 25). The README lists trip type, place, date, flexibility, passenger and cabin filters, with no result limit or pagination documented (10 of 20). No error responses documented (0). No tool annotations or retry guidance published (0). The README says places can be given as a city or an airport. No SDK, MCP only (5 of 15). 20 + 10 + 0 + 0 + 5 = 35.
LetsFG 83
The hosted MCP lists 24 tools, two of them hidden from the model as app-only, and present_flight_options cuts results to three picks (18 of 25). Result limits, cabin, time-window and stopover filters, refundable-only and airline-only flight filters (documented 25 October), and a search_id to page results without re-searching (18 of 20). Error codes an agent can act on, such as 402 search_allowance_exhausted versus payment_method_required, and missing_details with missing_fields (20). Idempotency keys on booking with retry guidance; no readOnlyHint or destructiveHint annotations in the stdio server source, re-read on 2 November (12 of 20). Three required search inputs, Python and JavaScript SDKs (15). 18 + 18 + 20 + 12 + 15 = 83.
Security & auth LetsFG +12
Kiwi.com MCP Server 54
No credentials. The README's install instructions for Claude, ChatGPT, Cursor, VS Code, Cline and Goose give only the URL, so there is no secret to leak and no way for an operator to scope, rotate or revoke access (20 of 30). The published tool searches and returns booking links, and purchases happen on kiwi.com, so nothing it does spends money. The earlier deduction for a second write tool rested on a struck reading and the earlier partial is kept (14 of 20). Results are Kiwi.com's own fare data. The August 2025 post says results come as tables with a fun fact about the destination. No injection guidance found (8 of 15). No audit log or per-call view for an operator (0). security.txt with a contact and a bug bounty link, a disclosure policy that says Kiwi.com will try to reply within two working days, and a HackerOne bug bounty. No SOC 2 or ISO 27001 statement found on the pages read (12 of 20). 20 + 14 + 8 + 0 + 12 = 54.
LetsFG 66
Hosted MCP uses OAuth 2.1 with PKCE (S256), dynamic client registration, five scopes split by search and book for flights and hotels, one-hour access tokens and rotating refresh tokens that revoke the grant on reuse. The Developer API uses an X-API-Key header, and we found no key-in-URL option (30). Search and book scopes are separate, the card is held rather than charged until a PNR exists, price changes come back as questions the traveller answers, and changing the card goes through an emailed link (16 of 20). Results come from airline and booking-site pages that LetsFG reads, and we found no injection guidance (5 of 15). get_agent_profile shows usage and bookings have status histories; no per-call log for the operator (7 of 15). SECURITY.md with security@letsfg.co and a 48-hour acknowledgement target, CI actions pinned to SHAs, no security.txt (404 again on 2 November), bug bounty or certification (8 of 20). 30 + 16 + 5 + 7 + 8 = 66.
Reliability LetsFG +10
Kiwi.com MCP Server 45
status.kiwi.com is a Statuspage site. Its page, read on 4 November, has components for Search API, booking, payments, customer support and partner systems, and none for the MCP server (15 of 20). Its incident history feed holds 25 entries, the newest dated 13 October 2021. A page that has posted nothing in five years isn't shown to post incidents, and it has no MCP component, so the empty window isn't credited as clean (20, as together-fine-tuning). No rate limits found in the README, the launch posts or the status page (0). No 429, Retry-After or backoff guidance found (0). No SLA (0). Kiwi.com's August 2025 post called the first version a prototype. Its 15 October 2026 post describes an in-house server in production use with no preview label (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.
LetsFG 55
A connector health dashboard at letsfg.co/developers/connectors/health with 1-hour to 7-day windows. Re-read on 2 November, it still renders client-side from the site's own /api/ path (which robots.txt closes), shows connectors rather than the API, and has no incident log (10 of 20). No readable incident history (5). Limits published with numbers, hosted MCP search at 10 per 10 minutes, 30 an hour and 100 a day per account (and per card once one is added), Developer API limit 1 to 200 (15). Over-limit answers 429 with retry_after_seconds and pauses of 10 minutes up to 24 hours, and booking takes an idempotency_key with documented retry behaviour (15). No SLA (0). The API, MCP and sandbox aren't labelled beta (10). 10 + 5 + 15 + 15 + 0 + 10 = 55.
Score by category
| Category | Weight | Kiwi.com MCP Server | LetsFG | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 55 | LetsFG +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 12 | 83 | LetsFG +71 |
| Agent ergonomics | 13% | 35 | 83 | LetsFG +48 |
| Security & auth | 14% | 54 | 66 | LetsFG +12 |
| Payments & pricing | 10% | 83 | 85 | LetsFG +2 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 13 | 88 | LetsFG +75 |
| Transparency & trust | 7% | 66 | 65 | Kiwi.com MCP Server +1 |
| Negative events | ≤15 | 0 | -7 | |
| Total | E 43.4/100 | B 66.5/100 |
Facts side by side
| Fact | Kiwi.com MCP Server | LetsFG |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Kiwi.com s.r.o. | LetsFG |
| Hosted endpoint | https://mcp.kiwi.com | https://letsfg.co/developers/api/v1 |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Price for flight search | free | $0.01 per call |
| x402 | no | no |
| Licence | Proprietary hosted service. The public repository holds only a README and has no licence file | MIT |
| Tools exposed | 1 | 24 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.LetsFG/letsfg |
| Last release | 2025-08-07 | 2026-10-17 |
| Terms last updated | no date given | 2026-09-19 |
| Privacy policy last updated | 2026-09-07 | 2026-09-19 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 12 stars | 2.1k stars, 157 npm/wk, 260 PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |
How the scores have moved
Verdicts
Kiwi.com MCP Server
A keyless flight search that Kiwi.com has run in-house since June 2026, with a booking link on every result and a HackerOne bug bounty behind it. It can't book, hold or cancel, and nothing published gives its tool schema, rate limits, changelog or terms. The only documentation is a README last changed in August 2025.
LetsFG
Hosted MCP with OAuth 2.1, PKCE, five scopes and rotating refresh tokens, plus REST, Python and npm clients and a keyless sandbox. Tickets are bought by a LetsFG booking agent after the hold, and the stdio tool descriptions still call search unlimited and booking free of LetsFG charges, against the docs' caps and the terms' service fee.
Before you call either
Kiwi.com MCP Server
- Add
https://mcp.kiwi.comas a streamable HTTP server with no key, as the README's install snippets show - Give origin, destination, dates and passengers, and say how flexible the dates are. The README allows up to 3 days either side
- Hand the user the booking link in each result. Booking, payment and changes happen on kiwi.com
- No rate limit or result-size control is documented, so cache searches rather than repeating them
LetsFG
- Start on
/v1/sandbox/with no key; the booking states, questions and timings match production - After
book_flight, pollget_flight_bookingevery 20 to 30 seconds and answer questions beforeexpires_at_ms; an unanswered price change fails the booking and releases the hold - Honour
retry_after_secondson a 429. Over MCP the limit is 10 searches per 10 minutes and 100 a day, and repeat overruns lengthen the pause up to 24 hours - Fetch results with
get_flight_resultsand thesearch_idrather than searching again, which spends allowance - Send the same
idempotency_keywhen retrying a booking after a timeout - Treat a 410 as a retired route and read the replacement path in its body
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Compare flights with Kiwi.com MCP, for Kiwi.com MCP Server
- Test a flight search with LetsFG sandbox, for LetsFG
Questions
Which is better for AI agents, Kiwi.com MCP Server or LetsFG?
LetsFG scores 66.5 (B) on agent readiness against Kiwi.com MCP Server's 43.4 (E), and leads in 6 of 7 scored categories.
Which is cheaper for flight search, Kiwi.com MCP Server or LetsFG?
Kiwi.com MCP Server, at free against $0.01 per call for LetsFG. These are the vendors' published prices for the job.
Do Kiwi.com MCP Server and LetsFG need an API key?
Kiwi.com MCP Server needs no key. LetsFG takes an API key or an OAuth sign-in.
Can an agent call Kiwi.com MCP Server and LetsFG without installing anything?
Yes. Kiwi.com MCP Server has a hosted endpoint at https://mcp.kiwi.com and LetsFG at https://letsfg.co/developers/api/v1.
Are Kiwi.com MCP Server and LetsFG open source?
No open-source release is listed for Kiwi.com MCP Server. LetsFG is open source (MIT).
Other comparisons with Kiwi.com MCP Server or LetsFG
- Booking.com Demand API vs Kiwi.com MCP Server
- Expedia Group Rapid API vs Kiwi.com MCP Server
- GoVisit Tools vs Kiwi.com MCP Server
- GoVisit Tools vs LetsFG
- Hotelbeds Hotel Booking API vs Kiwi.com MCP Server
- Kiwi.com MCP Server vs Lola
- Kiwi.com MCP Server vs ETG API (RateHawk)
- Kiwi.com MCP Server vs Trainline
- LetsFG vs Lola
- LetsFG vs Trainline
- Booking.com Demand API vs LetsFG
- Expedia Group Rapid API vs LetsFG
- Hotelbeds Hotel Booking API vs LetsFG
- LetsFG vs ETG API (RateHawk)
- Duffel Flights and Stays API vs Kiwi.com MCP Server
- Duffel Flights and Stays API vs LetsFG
- FlightClaw vs Kiwi.com MCP Server
- FlightClaw vs LetsFG
- Kiwi.com MCP Server vs LiteAPI (Nuitee Connect)
- Kiwi.com MCP Server vs Odessia
- Kiwi.com MCP Server vs Skyscanner Travel APIs
- Kiwi.com MCP Server vs Soar
- Kiwi.com MCP Server vs Travelport TripServices APIs
- LetsFG vs LiteAPI (Nuitee Connect)
- LetsFG vs Odessia
- LetsFG vs Skyscanner Travel APIs
- LetsFG vs Soar
- LetsFG vs Travelport TripServices APIs
Machine-readable
- This page as Markdown
/compare/kiwi-mcp-vs-letsfg.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kiwi-mcp.json·/api/v1/tools/letsfg.json - From a terminal
anchor compare kiwi-mcp letsfg(the CLI) - Over MCP
compare_tools {"a": "kiwi-mcp", "b": "letsfg"}at/mcp, no key