Autonomad Travel vs Voyagier — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Autonomad Travel vs Voyagier
In-depth architectural comparison of the Autonomad Travel and Voyagier MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Autonomad Travel
Travel & Transportation · Local stdio
Quality: 56/100 (Good) | Auth: other
Voyagier
Travel & Transportation · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Autonomad Travel if you need specialized Travel & Transportation tools running via a local process. Choose Voyagier if your workspace requires Travel & Transportation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Autonomad Travel when:
You need dedicated capabilities in the Travel & Transportation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: AGENT_DID, BOOKING_API_URL, IDENTITY_API_URL, REWARD_API_URL.
AI travel agent over MCP — live flights, hotels, activities, and events worldwide, then completes the booking on autonomad.ai (free signup at checkout, first month of Premium included).
Book real travel from your agent — flights, hotels & activities behind a price-gated checkout.
Autonomad Travel is categorized under Travel & Transportation and uses a local stdio subprocess. In contrast, Voyagier belongs to Travel & Transportation using local stdio subprocess. Select Autonomad Travel when you need capabilities focused on travel & transportation and Voyagier when you require tools for travel & transportation.
Reserve hotel rooms with commission transparency and on-chain delegation proof
manage_booking
Check-in, check-out, cancellation
submit_feedback
Post-stay structured reviews across all travel categories
check_rewards
Query $NOMD token balance, settlement history, and redemption options
Voyagier Tools (21)
doctor
Health check: auth, schema, state, version.
clients_list
Roster of CRM clients; `page`/`limit` page through it.
client_create
Idempotent by email; a plan needs a client.
plans_list
Owned + shared plans in one list, each tagged `relationship` `owner`/`shared`; the plan-discovery entry point. `relationship`/`active`/`page`/`limit` filter and page it.
search_destinations
Freeform text → ranked structured destinations; run before `plan_trip`.
plan_trip
Scaffold a plan + goal graph from a `template`; returns `nextSteps`. `travel_destination_id` (from `search_destinations`) is preferred over the freeform `destination`.
travellers_add
Adds the whole party in one call; required before search.
search_flights
Async — `optionCount 0` means poll options.
search_hotels
Prices are stay totals, not nightly.
search_activities
Bookable per slot.
get_selection_options
wait` (default true) polls the async fetch to completion.
refresh_options
Re-fetch a selection's options; `force` after a fetch error.