Flights take a route, dates, a cabin class and a sort order, and hotels take a coordinate pair, a radius, a price band and an occupancy. Because the hotel side is addressed by latitude and longitude, a geocoding step has to happen somewhere before the query — the server does not turn a place name into a location. today exists for the same practical reason: the other two want concrete dates.
A three-tool travel lookup server for flight and hotel availability, with hotels addressed by latitude and longitude rather than by place name.
- Flight search over a from/to route through search-flights, with departDate and returnDate, cabinClass and a sort order.
- Hotel availability around a point through search-hotels-by-coordinates, bounded by radius and a priceMin to priceMax band.
- Occupancy and currency control on hotel queries through adults, childrenAge, roomQuantity and currencyCode.
- Today, which resolves the current date so a relative request can be turned into concrete departDate and arrivalDate values before searching.
No account and no key. Hotel lookups need a latitude and longitude on hand, since search-hotels-by-coordinates takes a coordinate pair and a radius.
One command plus a key — npx travel-mcp-server, then supply credentials