ALLFLYGHTS vs Voyagier — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
ALLFLYGHTS vs Voyagier
In-depth architectural comparison of the ALLFLYGHTS 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
ALLFLYGHTS
Travel & Transportation · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: No auth required
Voyagier
Travel & Transportation · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose ALLFLYGHTS if you need specialized Travel & Transportation tools running via a hosted cloud SSE transport. 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 ALLFLYGHTS when:
You need dedicated capabilities in the Travel & Transportation domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: ALLFLYGHTS_PUBLIC_API_BASE_URL, ALLFLYGHTS_PUBLIC_API_KEY, PUBLIC_API_KEY_VAULT_URL, MCP_PUBLIC_API_KEY_SECRET_NAME, MCP_AUTH_TOKEN, MCP_AUTH_TOKEN_SECRET_NAME, MCP_TRANSPORT, PORT.
ALLFLYGHTS is categorized under Travel & Transportation and uses a remote streaming HTTP/SSE transport. In contrast, Voyagier belongs to Travel & Transportation using local stdio subprocess. Select ALLFLYGHTS when you need capabilities focused on travel & transportation and Voyagier when you require tools for travel & transportation.
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.