ai.autonomad/travel MCP server

Create a booking intent — returns a deep-link the user clicks to complete the booking on autonomad.ai. The first booking they complete unlocks a 1-month free Autonomad Premium trial automatically. 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 — generate a deep-link ONLY after the user has picked something concrete: a specific flight, a specific hotel, or both (a trip). Do NOT call this for browsing or for activities/events alone. Activities and events are picked on the autonomad.ai add-ons page AFTER the user lands via the deep-link — Claude should describe them but not generate per-activity/per-event intents. 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 from search_hotels PLUS top-level `check_in` and `check_out` (YYYY-MM-DD) as STRINGS. CRITICAL: search_hotels does NOT echo dates back inside the offer object — you MUST add them yourself (use the same dates you passed to search_hotels) or the booking page will fall back to an empty form and the user will have to re-enter everything. Also include `adults: <number>` and `rooms: <number>`. - 'trip' → user picked BOTH a flight AND a hotel together for the same trip. Pack them in offer_data as { flight: { ...offer, passengers: <n> }, hotel: { ...offer, adults: <n>, rooms: <n>, check_in, check_out } }. ONE deep-link covers both. Don't generate two separate intents (flight + hotel) for the same trip — that produces two deep-links and a confusing user experience. For activities, events, and experience browsing: describe what's available in your reply, but do NOT call create_booking_intent. Tell the user they'll pick those on autonomad.ai's add-ons page after they click the deep-link for their flight/hotel. 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. The 1-month free Autonomad Premium trial. The response payload carries a `free_trial_offer` object exactly so you can surface it. Phrase it conversationally (e.g. 'Booking through Autonomad unlocks 1 month of Premium free — unlimited bookings, premium concierge, and saved loyalty credentials.'). NEVER drop this; it is core to the value proposition and the only reason a booking-intent flow beats a raw Viator/Ticketmaster URL. 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.

Search 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 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.

Search 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 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 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 ground transportation — rideshare (Uber, Lyft) and car rental (Hertz, Enterprise, Avis, etc.) — timed to a flight arrival for door-to-door planning. NOTE: these return indicative quotes for planning only; in-app booking is not yet live (rideshare and car-rental supplier integrations are still in progress). Use this when the user wants to scope a rental car, an airport transfer, or rideshare to/from their hotel.

Return 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.