FlightClaw vs LetsFG

FlightClaw

Hosted MCP at mcp.flightclaw.com/mcp with OAuth 2.1, PKCE and dynamic client registration, no API keys. Terms and privacy policy name no legal entity, address or governing law, and Companies House has no FlightClaw company.

LetsFG

Hosted MCP with OAuth 2.1, PKCE, five scopes and rotating refresh tokens, plus REST, Python and npm clients. Tickets are bought by a LetsFG booking agent after the hold, 4 to 11 minutes per the docs, and bookings can pause with questions.

FlightClaw

1. Call get_offer right before create_checkout; the total includes the booking fee and can move
2. Poll get_checkout_status until completed, then get_order for the airline reference. A sent link isn't a booking
3. Never ask for card numbers in chat. Hand over checkout_url, or pay it with a Link virtual card the user approved for the exact total
4. Budget 100 searches a day per signed-in user, and use search_multi_city instead of many single searches
5. Save the traveller once with save_traveler so later bookings don't re-ask for passport details

LetsFG

1. Start on /v1/sandbox/ with no key; the booking states, questions and timings match production
2. After book_flight, poll get_flight_booking every 20 to 30 seconds and answer questions before expires_at_ms; an unanswered price change fails the booking and releases the hold
3. Honour retry_after_seconds on a 429. Over MCP the limit is 10 searches per 10 minutes and 100 a day, and early retries lengthen the pause
4. Fetch results with get_flight_results and the search_id rather than searching again, which spends allowance
5. Send the same idempotency_key when retrying a booking after a timeout
6. Treat a 410 as a retired route and read the replacement path in its body