google-flights-proto-mcp
Related Servers
Alternatives to google-flights-proto-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables real-time flight search on Google Flights, letting AI agents find flights, explore date ranges, and locate airports through native MCP tools.MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to search Google Flights for trips, filter for Starlink-equipped flights, enforce connection rules, compare fare premiums, and manage saved search presets through MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceEnables flight search and fare calendar exploration by interacting with Google Flights' API, supporting detailed filters for origin, destination, dates, cabin class, airlines, and more.3,876 PyPI3,193MIT
- AlicenseAqualityCmaintenanceEnables searching Google Flights and getting structured, price-sorted flight options locally through MCP clients like Claude or Codex, with no API key or central server required.1MIT
- AlicenseAqualityBmaintenanceEnables real-time flight fare searches across date ranges and multiple destinations, with historical price insights and booking links. Provides one-way and round-trip search tools through MCP.41MIT
- FlicenseAqualityAmaintenanceEnables 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-
TDQS
Scored across 3 tools
build_protobuf_search_url is clearly distinct as a URL builder, but discover_and_rank_complete and search_and_verify_top overlap heavily since both perform the same core search and ranking flow, differing only in the verification step. The descriptions help, but an agent could easily pick the wrong one when it only needs unverified results.
All tool names use snake_case and begin with a verb, which is a solid pattern. The minor inconsistency is that build_protobuf_search_url uses a simple verb_noun structure while the other two use verb_and_verb_complement, making the set slightly uneven but still readable.
Three tools is a reasonable size for a focused flight-search server that exposes a small pipeline: build URL, run search and ranking, then optionally verify. Each tool has a real purpose, though the set is slightly thin if broader flight-search operations were intended.
The tools cover the main workflow from URL construction through ranking and verification, so most end-to-end flight search needs are addressed. Minor gaps exist such as no tool to view raw intermediate protobuf/HTTP responses, but agents can work around this by chaining the available tools.