Google Flights Fares MCP Server
Related Servers
Alternatives to Google Flights Fares MCP Server
No user-submitted related servers found.
Related Servers
- 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
- 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 searching Google Flights through MCP and retrieving JSON itineraries with prices, durations, stops, flight legs, and CO2 emissions, using filters for dates, passengers, class, airlines, stops, times, and emissions.316 npmMIT
- AlicenseAqualityBmaintenanceIntegrates Google Flights data into AI workflows for natural language flight searches, price comparisons, flexible date searches, and multi-city itinerary planning with support for various cabin classes and passenger types.98MIT
- AlicenseAqualityBmaintenanceEnables searching and analyzing Google Flights data including prices, emissions, cabin classes, layovers, and price tracking, all without an API key.12205 npm5ISC
- AlicenseAqualityDmaintenanceConnects AI agents to Google Flights data, enabling retrieval of flight information, cheapest options, time-filtered flights, and best recommendations.430MIT
TDQS
Scored across 1 tool
Only one tool exists, so there is nothing to confuse it with. Its purpose—searching Google Flights for a route and dates—is crystal clear from the name and description.
A single descriptive snake_case verb_noun name (get_google_flights_fares) with no competing conventions to clash with. It is readable and self-explanatory.
One tool is thin even for a narrowly scoped fare-search server; there is no way to resolve airport codes, propose flexible dates, or fetch details. The single tool does earn its place, but the surface is minimal.
The core search flow is covered, but the surface is a dead end: no filters (cabin class, max stops, passengers), no date-flexibility option, and no way to retrieve a specific fare's details or booking link. Agents can work around this only by re-calling with different arguments.