Autonomad Travel vs LetsFG — Flights & Hotels
A side-by-side look at the Autonomad Travel and LetsFG — Flights & Hotels MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Autonomad Travel for travel & transportation work as a local process; choose LetsFG — Flights & Hotels for travel & transportation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Autonomad Travel when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
AGENT_DID, BOOKING_API_URL, IDENTITY_API_URL, REWARD_API_URL. - You want tools like
search_hotels, search_flights, search_dining.
Choose LetsFG — Flights & Hotels when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_flights, resolve_location, book_flight.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 61/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | AGENT_DIDBOOKING_API_URLIDENTITY_API_URLREWARD_API_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 2,186 |
| Directory activity | 4 views 0 installs 0 upvotes | 2 views 1 installs 0 upvotes |
| Tools | 7 | 14 |
| Full listing | View Autonomad Travel | View LetsFG — Flights & Hotels |
Tools & capabilities
Autonomad Travel tools 7
search_hotelsSearch hotels, lodging, accommodations, resorts, and places to stay for a trip. Filter by city, country, check-in/check-out dates, room type, nightly price, star rating, and amenities (pool, gym, wifi, etc.). Returns matching properties with rates, photos, and availability across 2M+ properties (LiteAPI). Use this when the user wants to book a hotel, find a place to stay, compare lodging options, or pick a resort.search_flightsSearch airline flights / airfares between two cities by date, cabin class (economy / premium economy / business / first), and number of passengers. Returns available flights from 800+ airlines (Duffel) with real-time pricing, schedules, and stops. Uses IATA airport codes (e.g., MIA, JFK, LAX, LHR). Use this when the user wants to book a flight, fly somewhere, find airfare, or compare airlines.search_diningSearch restaurants and dining options by city, date, time, cuisine, party size, neighborhood, and price range. PLANNING ONLY — this returns restaurant details and indicative availability; Autonomad does not place reservations, and the user completes any booking with the restaurant directly. Use this when the user wants to find, compare, or shortlist somewhere to eat on a trip.search_activitiesSearch tours, experiences, attractions, sightseeing, and things to do via Viator (200K+ activities worldwide). Filter by city, date range, and category (food tours, walking tours, museums, snorkeling, sailing, hiking, sunset cruises, cooking classes, day trips, etc.). Returns activities with photos, ratings, durations, and per-person pricing. Use this when the user wants to plan day activities, find tours, book experiences, fill a trip itinerary, or pick attractions.search_eventsSearch live events, concerts, sports games, theater, comedy, and shows in a city (Ticketmaster + SeatGeek catalog). Filter by city, date range, category (music / sports / arts / theater / family / comedy), and keyword (artist name, team name, show title). Use this when the user wants tickets to a concert, a sports game, a Broadway show, or any live event during their trip.create_booking_intentCreate a booking intent — returns a deep-link the user clicks to complete the booking on autonomad.ai. Signing up is free, with no trial and no subscription. ALWAYS call this instead of trying to book directly through MCP — bookings require payment + identity verification that must happen on the web. WHEN TO CALL — two distinct triggers: (a) PICK intents (flight / hotel / activity / event / trip): call AFTER the user has chosen a specific offer. (b) BROWSE intent ('experiences'): call IMMEDIATELY in the SAME assistant turn that you ran search_activities and/or search_events for a browse query. Do NOT wait for the user to ask 'where's the link?' — the user already told you they want this when they asked to browse. Showing search results without also producing the deep-link is a UX failure: it forces the subscriber to manually request something they already implicitly asked for. INTENT TYPE GUIDE — pick exactly one: - 'flight' → user picked a flight only. offer_data = the flight offer object verbatim from search_flights, PLUS a top-level `passengers: <number>` field (the number of travelers the user originally requested — search_flights individual offers don't echo this back, so you must add it explicitly). - 'hotel' → user picked a hotel only. offer_data = the hotel offer object verbatim from search_hotels (or just {city, check_in, check_out} if you want to send them to a hotel-search results page rather than a specific hotel). Include `adults: <number>` and `rooms: <number>` so the booking page pre-fills the right party size. - 'activity' → user picked a Viator activity. offer_data = the activity offer. - 'event' → user picked a Ticketmaster/SeatGeek event. offer_data = the event offer. - 'trip' → user picked MULTIPLE things together (e.g. flight + hotel for the same trip). Pack them in offer_data as { flight: { ...offer, passengers: <n> }, hotel: { ...offer, adults: <n>, rooms: <n> }, activities: [<activity_offer>, ...] } — only include the keys the user actually picked. ONE deep-link covers all of them. - 'experiences' → BROWSE intent. The user wants to look at all activities AND events for a destination + date window WITHOUT picking a specific one. STRONGLY PREFER this over picking one activity yourself when the user asks to 'browse', 'see what's available', 'look at experiences in X', or just describes a destination/date range with no specific tour name. offer_data shape: { destination: 'City, Region', date_from: 'YYYY-MM-DD', date_to: 'YYYY-MM-DD', travelers?: <number>, activity_keywords?: [...], event_categories?: [...] }. The deep-link lands the subscriber on autonomad.ai's add-ons step with destination + dates pre-filled, where Viator activities and Ticketmaster/SeatGeek events for the area are surfaced together — and they can edit dates / traveler count inline. Use this whenever the subscriber's intent is 'show me everything', not 'I want this one specific tour'. Prefer 'trip' when the user said something like 'book me a flight and hotel for X' and you have both picked. Prefer 'experiences' when the user is asking to BROWSE activities/events without picking one (e.g. 'experiences between July 9 and July 13 near Stintino' → ONE deep-link, not 24 individual activity intents). Don't generate two separate intents (flight + hotel) for the same trip — that produces two deep-links and a confusing user experience. USER-FACING REPLY REQUIREMENTS — every time you create a booking intent, your reply text MUST include: 1. The deep_link as a clickable markdown link, e.g. '[Complete on autonomad.ai →](<deep_link>)' or 'Open: <deep_link>'. 2. That the account is free. Autonomad costs the traveller nothing — no subscription, no trial, no card required to sign up; they pay only for the travel they book. NEVER describe a trial, a free month, or Premium: none of those exist, and promising one is a claim we cannot honour. 3. The link expiry window (e.g. '~30 minutes — say the word and I'll regenerate if it lapses.'). CRITICAL: always echo the original passenger / adults / travelers count into offer_data. Without it the booking page defaults to 2 travelers regardless of what the user asked for.get_capabilitiesReturn the server's version, mode (human vs autonomous-agent), API base, and the list of currently-exposed tools. Useful for the LLM to confirm tool-schema compatibility before issuing a sequence of calls — call once at session start if you need to branch on capabilities.
LetsFG — Flights & Hotels tools 14
search_flightsSearch hundreds of airlines for live flight prices — completely FREE, unlimited, read-only. Returns structured offers with prices, airlines, times, durations, and stopovers. Some offers carry `starlink` for in-flight Starlink Wi-Fi: "confirmed_all" / "confirmed_some" mean the carrier has FULLY fitted that aircraft type, "likely_all" / "likely_some" mean the rollout on that type is underway but incomplete. State only "confirmed_*" as fact; describe "likely_*" as "the airline is fitting this aircraft type, not guaranteed on your flight". Anything ending in "_some" has at least one leg WITHOUT it. An absent field means no information, NOT an absence of Wi-Fi. Covers airlines across all continents including low-cost carriers. Search is async: this tool polls for you, including waiting out the late split-ticket merge. Some offers are SPLIT TICKETS: two separately-issued tickets through a hub, each leg booked from whatever is cheapest for it (usually two different airlines), because no one seller offers the combination as a single ticket. They carry `split_ticket: "true"`, `combo_type: "virtual_interlining"` and `self_transfer: "unprotected"`. ALWAYS tell the user when an offer is a split ticket and what unprotected means: the tickets are not linked, so if the first flight is late and the connection is missed, the second airline owes nothing — no rebooking, no refund. Never present a split ticket as though it were one through-fare. Requires LETSFG_BEARER_TOKEN or LETSFG_API_KEY. See letsfg://guide resource for the full authenticate->search->book workflow.resolve_locationConvert a city/airport name to IATA codes. Always call before search_flights if you only have a city name. Read-only, safe to call multiple times.book_flightBook a flight from a search result. FLOW: authenticate (once) -> search_flights -> book_flight CHARGES: nothing from LetsFG. A completed booking pays the airline prices from airlines and the major booking sites. RESULT: either {"booked": true, "order_id": "..."} or {"booked": false, "booking_url": "..."} — the second means the booking genuinely did not complete and nothing was charged. That is a normal outcome, NOT a transient error: do not retry, give the user the booking_url. SAFETY: use REAL passenger details — names must match passport, email receives the e-ticket.get_flight_bookingPoll a flight booking started by book_flight. REQUIRED to learn the outcome: on a PFS Bearer token book_flight returns a booking_ref and state "booking_in_progress", not a PNR - the booking itself takes 4-11 minutes. Call it every 20-30 s with that booking_ref until state is terminal: completed -> PNR issued, card charged failed -> the hold was released, nothing was charged needs_attention -> a human is looking at it; do NOT rebook Do not rebook while the state is still moving, and do not treat a slow poll as a failure - the money is HELD, not taken, until the airline confirms. Refs last one hour past the booking start.answer_booking_questionAnswer the question a paused booking is waiting on. get_flight_booking returns `awaiting_choice` when the booking agent has stopped mid-checkout holding a cart: at the airline's own seat map, at a paid extra it has just priced, or at a fare that moved. NOTHING PROGRESSES UNTIL YOU ANSWER, and the cart expires. Put the question to the traveller with the options and the time left, then send their answer here. kind "seat" -> seats: [{ d: "12A" }, ...] from the map you were shown, or skip: true kind "extra" -> confirm: true to take it (a bag, or a moved fare), or confirm: false / skip: true to decline Always pass the `round` from `awaiting_choice` - it says WHICH question you are answering. A return trip pauses twice, and an answer without it could seat the wrong leg.resolve_hotel_cityConvert a place name to the supplier city id that search_hotels needs. Always call this first if you only have a city name. Read-only and safe to repeat. Use `Id` from the first result as city_id and `Name` as city_name.search_hotelsSearch real, bookable hotel inventory. Requires a connected payment method — the SAME one that authorises flight booking. That applies to search too, not just booking, because a search opens a real session at the supplier. Every rate type is returned, refundable and non-refundable; each offer's `refundable` and `free_cancellation_until` say which. `price` is what the guest pays, in `currency` (USD unless you pass currency): the supplier's cost plus `markup_rate` (6.4% for Revolut Pay or an EEA card, 8.3% for a card issued outside the EEA). Nothing is added at booking. Keep the chosen offer whole — book_hotel needs its `session_id`, `combination_id_v2`, `price`, `expected_cost`, `currency` and `fx_rate`. Takes up to a few minutes.book_hotelBook one hotel rate. The offer's full price is HELD on the connected Revolut payment method (authorised, not taken); LetsFG books and pays the supplier; the hold is captured only once the supplier has confirmed. If the booking fails for any reason the hold is released and nothing is charged. There is no reservation fee, no deposit and no pay link. Returns a booking_job_id, NOT the booking — a booking takes minutes. Poll get_hotel_booking every ~20s until status is succeeded, failed or attention; all three are final. Copy expected_price (the offer's price), expected_cost, currency and fx_rate from the chosen offer exactly. A USD offer sent without its currency is refused (400 price_mismatch). Guest names, phone and e-mail are checked before anything is held (400 invalid_details). guests needs ONE name per guest in the room, children included — adults first, then children in child_ages order. Do NOT call book_hotel again for a booking whose job is running — poll it; a retry returns the same job (duplicate: true).get_hotel_bookingCollect the result of a booking started with book_hotel. Poll every ~20s. status is in_progress, succeeded, failed or attention; the last three are final — stop polling. - succeeded: confirmation, hotel, room, total_price + currency (what the guest is charged), supplier_paid + supplier_currency, payment_status, refundable, free_cancellation_until, cancellation_ladder and terms. - failed: error, written for the guest. The hold was released; nothing was charged. - attention: error (+ confirmation if known). The outcome could not be settled automatically; the hold is kept (nothing charged) while a person checks with the supplier. Do NOT book again. The guest is e-mailed in every case. Read-only and safe to repeat.cancel_hotel_bookingCancel a hotel booking made by this account and refund the guest. A zero-charge cancellation (a refundable rate before free_cancellation_until) refunds the charge in full; a cancellation that would cost money is refused (409) — the hotel's own ladder is in the booking terms. Takes over a minute; if it times out do NOT assume it failed — re-check before retrying.authenticateExplain how to connect a card so this server can search and book. Nothing is charged to connect — a 0.00 Revolut setup that saves the card so a booking can be charged later. Call with no arguments. It returns the current instructions and add_card_url (https://letsfg.co/connect). A PERSON must approve once in a browser — there is no endpoint that mints a token from card details, so do not ask the user for card numbers and do not try to automate this step. Two ways in: (a) add LetsFG as a connector in an assistant that supports remote MCP servers and approve it, or (b) any OAuth-capable client can register itself — see https://letsfg.co/for-agents, section "Option B". Both land on the same card screen. RETIRED 2026-09-02: the Stripe lanes (setup_url, setup_session_id, payment_method_id, card_token) and every token they issued. Passing them now fails. This does NOT create a Developer API billing account. Do not use connect_payment for this.connect_payment[Developer API only — you almost certainly want `authenticate` instead] Mints a one-time link for connecting a payment method to a PAID prepaid Developer API account. Nothing is charged to connect and card details never touch LetsFG: a PERSON opens the returned connect_url in a browser and saves a card, Revolut Pay or Google Pay there. Do not ask a user for card numbers and do not try to automate that step. Refuses to run unless LETSFG_API_KEY is set, because agents kept calling this and creating billing accounts they did not need. Replaced setup_payment on 2026-09-08, when the Stripe lane was retired.- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Autonomad Travel
{
"mcpServers": {
"autonomad1-autonomad-travel": {
"command": "npx",
"args": [
"-y",
"autonomad-travel"
],
"env": {
"AGENT_DID": "YOUR_AGENT_DID_HERE",
"BOOKING_API_URL": "YOUR_BOOKING_API_URL_HERE",
"IDENTITY_API_URL": "YOUR_IDENTITY_API_URL_HERE",
"REWARD_API_URL": "YOUR_REWARD_API_URL_HERE"
}
}
}
}
LetsFG — Flights & Hotels
{
"mcpServers": {
"letsfg-flights-hotels": {
"command": "npx",
"args": [
"-y",
"letsfg-mcp"
]
}
}
}
Frequently asked questions
Autonomad Travel is categorized under Travel & Transportation and uses a local stdio subprocess. LetsFG — Flights & Hotels belongs to Travel & Transportation and uses a local stdio subprocess. Pick Autonomad Travel for travel & transportation work and LetsFG — Flights & Hotels for travel & transportation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Autonomad Travel is listed as free. Auth: other. LetsFG — Flights & Hotels has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add autonomad1-autonomad-travel and letsfg-flights-hotels as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Autonomad Travel has a quality signal of 61/100 (Good) with 4 views, 0 installs and 2 GitHub stars. LetsFG — Flights & Hotels has 69/100 (Great) with 2 views, 1 installs and 2,186 GitHub stars.