travel-mcp
Related Servers
Alternatives to travel-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables searching Google Flights for one-way, round-trip, and multi-city itineraries, plus fare tracking and price alerts via SerpAPI.9MIT
- FlicenseAqualityBmaintenanceEnables LLMs to search Google Flights for one-way and round-trip flights, with configurable filters for airports, dates, passengers, cabin, stops, airlines, price, bags, and more, returning booking links and detailed trip information.1-
- AlicenseNot gradedqualityBmaintenanceEnables flight search and fare calendar exploration by interacting with Google Flights' API, supporting detailed filters for origin, destination, dates, cabin class, airlines, and more.5,091 PyPI3,504MIT
- AlicenseAqualityBmaintenanceEnables searching and analyzing Google Flights data including prices, emissions, cabin classes, layovers, and price tracking, all without an API key.12205 npm5ISC
- AlicenseAqualityDmaintenanceSearch flights using Google Flights data via SerpAPI, covering all airlines including low-cost carriers like Ryanair and easyJet.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search for real-time flights between airports using the SearchAPI.io Google Flights API, returning prices, schedules, airlines, and carbon emissions.-
TDQS
Scored across 4 tools
Each tool has a distinct role: single/round-trip flight search, multi-city search, continuation of an existing search via token, and booking option retrieval. The boundary between search_flights and search_multi_city is clear from the trip type, and the token-based tools are explicitly scoped.
All tools use consistent snake_case verb_noun naming: search_flights, search_multi_city, get_next_flights, get_booking_options. The pattern is predictable and easy for an agent to follow.
Four tools are well-scoped for a focused flight-search server. Each tool earns its place in the search and booking-option workflow, with no redundant or filler tools.
The surface covers core flight search workflows: one-way/round-trip, multi-city, continuation, and booking options. Minor gaps exist around ancillary needs like airport lookup or explicit offer details, but core workflows are covered without dead ends.