Autonomad Travel vs MCP Server
A side-by-side look at the Autonomad Travel and MCP Server 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 MCP Server for travel & transportation over a hosted endpoint. 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 MCP Server when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
departi_check_visa, departi_track_schengen, departi_check_tax.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 61/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | other | No auth required |
| 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 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 7 | 7 |
| Full listing | View Autonomad Travel | View MCP Server |
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.
MCP Server tools 7
departi_check_visaReturns the entry/visa options for a traveller of a given nationality (passport) going to a destination for a stated purpose and length of stay. Each option includes: visa/permit type, whether a visa is required, maximum stay, whether remote/on-site work is allowed, cost, processing time, and application/renewal notes — sourced from official immigration authorities. Use this for "what visa do I need / can I stay N days / can I work remotely here". To count days already spent against the 90/180 limit use departi_track_schengen; for the tax consequences of staying use departi_check_tax. Tip: nationality should be the traveller's most favorable passport — multi-nationals may have better entry on one passport.departi_track_schengenCalculates Schengen 90/180 short-stay status from a list of stays. Returns: days used and days remaining in the rolling 180-day window, a status (safe | warning | critical | exceeded), the projected date the limit would be reached at the current pace, and — for residence/digital-nomad-permit holders — a count that excludes days in the permit-issuing country while still counting every other Schengen state (with a note of which country is excluded). Use for non-EU travellers tracking the 90-days-in-180 limit. Note: EU/EEA nationals have free movement (not counted); a residence permit exempts only its issuing country, not the rest of Schengen.departi_check_taxAssesses tax-residency risk and double-tax-treaty position for a traveller in a destination. Returns: whether the stay risks triggering destination tax residency (the day threshold and the country's day-counting method), the relevant treaty provisions between the traveller's tax-residence country and the destination (employment income, tie-breaker, social security, withholding), any special or digital-nomad tax regime, and — for US citizens — FEIE / Physical-Presence-Test context. Advisory only, not tax advice. Use for "will staying here make me tax resident / what does the treaty say / how are my days counted". Note: any US citizenship triggers worldwide/citizenship-based obligations regardless of residence or other passports.departi_search_accommodationSearches bookable accommodation in a destination for given dates and returns a ranked list of stays, each with: name, property type, nightly price (in the requested currency), star rating, guest rating, key facilities (e.g. wifi, kitchen), a persona/traveler-type fit score, and a booking deep-link. Curated and scored for the traveller's persona and trip type — e.g. long-stay nomad apartments with kitchen + fast wifi vs weekend hotels. Use when the user needs a place to stay; for getting there use departi_search_transport, for things to do use departi_search_experiences. Returns an empty list if no inventory matches.departi_search_transportSearches flights between two places and returns a ranked list of options, each with: carrier, price (in requested currency), cabin class, total duration, number of stops, departure & arrival times, and a booking deep-link. Flights are sourced across providers (Duffel + Travelpayouts) for broad full-service and low-cost coverage. Use for "how do I get from A to B by air". For where to stay use departi_search_accommodation; for things to do use departi_search_experiences. Prices are indicative — book via the returned link. Returns an empty list if no route is found. Ground/rail/bus is not offered through this tool.departi_search_experiencesSearches bookable tours, activities and local experiences in a destination and returns a ranked list, each with: title, category (cultural / culinary / adventure / wellness / nature), duration, price (in requested currency), a persona-fit score, and a booking deep-link. Matched to the traveller's persona/personality. Use for "what can I do in X". For a place to stay use departi_search_accommodation; to get there use departi_search_transport. Returns an empty list if nothing matches the filters.departi_get_profileReturns the authenticated user's Departi profile: nationality, tax residence, subscription tier, traveller persona, and preferences. No PII (name, email, date of birth) is returned — only the fields the other tools need for personalisation. Requires authentication (OAuth). Use to personalise the other tools' answers, or to answer "where do I stand right now". Read-only; takes no parameters.
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"
}
}
}
}
MCP Server
{
"mcpServers": {
"departi-mcp-server": {
"url": "https://mcp.departi.eu/v3"
}
}
}
Frequently asked questions
Autonomad Travel is categorized under Travel & Transportation and uses a local stdio subprocess. MCP Server belongs to Travel & Transportation and uses a remote HTTP/SSE transport. Pick Autonomad Travel for travel & transportation work and MCP Server 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. MCP Server has no declared pricing — check the project's own site. Auth: no auth required. 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 departi-mcp-server 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. MCP Server has 67/100 (Great) with 2 views, 0 installs and 0 GitHub stars.