BoostedTravel

What BoostedTravel MCP server does

The BoostedTravel MCP server connects an AI agent to live flight and hotel inventory. Flight searches return structured offers containing prices, airlines, schedules, durations, stopovers, and other itinerary details. Coverage includes airlines across all continents, including low-cost carriers. Hotel searches return real, bookable inventory, but only free-cancellation, pay-later rates are included.

The service supports both discovery and booking. Agents can search flights, reserve or book an offer, poll booking progress, search hotels, book a selected room, retrieve the final hotel result, and cancel a hotel reservation. It also provides location-resolution tools for converting city or airport names into the identifiers required by search calls.

How it works

The BoostedTravel MCP server uses asynchronous workflows for searches and bookings. Before a flight search, resolve a city name to an IATA code with resolve_location. Flight search itself waits for the provider response, including delayed split-ticket processing. If an offer has split_ticket: "true", the agent must clearly explain that the itinerary contains separately issued tickets and an unprotected connection. A missed connection caused by a late first flight does not obligate the second airline to rebook or refund the passenger.

The normal flight path is authenticate, search, and book. A bearer-token booking may return booking_in_progress with a booking_ref; poll get_flight_booking every 20–30 seconds until the state is completed, failed, or needs_attention. Do not rebook while the status is changing. A booking_url from book_flight means no booking completed and no charge was made, so it should be given to the user rather than retried automatically.

Hotel operations have a similar sequence: resolve the supplier city, search, book, and poll get_hotel_booking. Hotel booking returns a job identifier rather than an immediate confirmation. The reservation fee is charged before the room is committed, while the remaining balance is paid to the supplier through the returned payment link.

Setup and configuration

Set either LETSFG_BEARER_TOKEN or LETSFG_API_KEY. A bearer token is intended for the standard agent flow; the Developer API key enables Developer API-only operations such as offer unlocking, profile access, and prepaid API billing. unlock_flight_offer is a legacy Developer API path and is not part of the normal bearer-token booking flow.

The authenticate tool explains how to connect a card and returns the current connection instructions plus an approval URL. A person must approve the card connection in a browser. Agents must not request or automate entry of card numbers. Connecting the card does not charge the user, but the same card is required for hotel searches and flight bookings.

The service can also be used as a hosted MCP endpoint, so local installation is not required for the documented agent setup. The README also lists letsfg for Python and letsfg-mcp for npm, but the supplied material does not specify a directly runnable local server command.

Tools and capabilities

• Resolve airport, city, and hotel-supplier locations.
• Search live flights across hundreds of airlines.
• Inspect Starlink indicators when present; confirmed_* values indicate confirmed fitting, while likely_* values indicate an incomplete rollout that is not guaranteed on the selected flight.
• Book flights and poll delayed booking outcomes.
• Search, book, poll, and cancel hotel reservations.
• Load the travel workflow guide through the MCP resource or load_resources.

Limitations and notes

Flight booking uses real passenger information, and passenger names must match passports. Hotel booking is not idempotent: repeating a successful call can create another reservation and charge another fee. Hotel cancellation is free until the supplier deadline, but the 5% reservation fee is not refunded; after the deadline, the supplier's cancellation ladder can apply.

The Stripe setup fields and tokens described as retired on September 2, 2026 must not be used. The current card connection flow is handled through authenticate and the browser approval process.