
Official MCP RegistryListed
Wego
Search live flight and hotel prices on Wego. Get schedules, public holidays and booking links.
First seen 17 Nov 2026. Evidence as of 18 Nov 2026.
10
Tools
From an anonymous probe
1
Source listings
Each with its own history
3
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| flights_one_way_price | Shows cheapest one-way flight prices across a date range. Returns daily prices with price band thresholds for comparison. Use with origin/destination IATA codes from places_find_location. Defaults to next 6 months if no dates provided. | Read-only |
| flights_schedule | Gets the current published timetable of nonstop flights between two cities: airlines, flight numbers, departure and arrival airports and times, duration, and operating periods (dates, weekdays and aircraft). Connecting flights are not listed: use flights_search for those and for fares on a date. Accepts city or airport IATA codes from places_find_location; an airport code gives its city's timetable. Results are paged: when metadata.hasMore is true, call again with page + 1. Optionally filter by airline code. | Read-only |
| flights_search | Searches for flights between airports or cities. Not for flight status, price tracking, visa information, bookings, or reservation management. Polling flow: 1. First call with newSearch → creates search session, returns searchId immediately (status: "created", pollAgainInSeconds: 5). 2. Wait pollAgainInSeconds, then call again with searchId → returns flight results with status "incomplete" (cheaper fares still arriving, pollAgainInSeconds says when to call again) or "complete" (final results). 3. While status is "incomplete", wait pollAgainInSeconds and call again. Stop when status is "complete". If it is still "incomplete" after 3 reads, use the results you have. A search is complete about 30 seconds after it is created. After that, every read (another page, new filters or sorting) returns status "complete" at once. Parameters: - newSearch: Route (from/to as IATA codes), dates (fromDate, toDate in YYYY-MM-DD), passengers, and cabin class. Omit toDate for one-way trips. - Defaults when not specified: 1 adult, 0 children, 0 infants, economy cabin. - filters: Include only when the user mentions specific preferences (airlines, stops, times, price range, etc.). - sorting: A single string value. Options: score_desc (recommended, default), price_asc (cheapest), duration_asc (fastest), leg1_departure_time_asc/desc (outbound departure), leg2_departure_time_asc/desc (return departure, round-trip only). - page, pageSize: Which page of the ranked trips a searchId read returns. page 1-100 (default 1), pageSize 1-50 (default 20). Out-of-range values are rejected. Paging: every searchId read returns metadata {page, pageSize, resultCount, totalCandidates, hasMore}. totalCandidates counts trips matching the filters across all pages; resultCount counts this page. For more trips, repeat the searchId with the same filters and sorting and page + 1 while hasMore is true. Featured trips appear on page 1 only, and labels (best_value, cheapest, cheapest_direct) are judged over all matching trips, not the page. Filter options: a page-1 read with searchId returns filterOptions with the airlines, alliances, bookingSites and stopoverAirports found in this search; page 2 and later do not. While status is "incomplete" the lists are partial and can grow; when status is "complete" they are final. Each entry is { code, name, price }, where price is the cheapest per-person price in the search currency, before filters. Every code is a valid value for the filter of the same name. Use these codes in filters on the next read instead of guessing. Time filtering (two approaches, mutually exclusive per dimension): 1. Time blocks (6-hour windows) — for broad preferences: - Options: "midnight" (12am-6am), "morning" (6am-12pm), "afternoon" (12pm-6pm), "night" (6pm-12am) - Example: outboundDepartureTimeBlocks: ["morning", "afternoon"] = depart before 6pm 2. Time ranges (minute precision) — for specific time requests: - Format: {min: minutesFromMidnight, max: minutesFromMidnight}, range 0-1440 - Example: "flights after 10pm" → outboundDepartureTimeRange: {min: 1320, max: 1440} - Example: "depart 8am-1pm" → outboundDepartureTimeRange: {min: 480, max: 780} - Supports wraparound: {min: 1380, max: 60} = 11pm-1am (crosses midnight) Time blocks and time ranges cannot both be specified for the same dimension (e.g., outboundDeparture). Refinement: Provide the searchId from a previous response with updated filters or sorting. Refinement replaces all previous filters and sorting entirely — include existing values alongside new ones to preserve them. Example — changing return to after 10pm while keeping existing airlines ["SQ", "KE"], outbound 6am-8am, and price_asc sorting: { "searchId": "abc", "filters": { "airlines": ["SQ", "KE"], "outboundDepartureTimeRange": { "min": 360, "max": 480 }, "inboundArrivalTimeRange": { "min": 1320, "max": 1440 } }, "sorting": "price_asc" } Default behavior: - One date provided → one-way trip - Return date mentioned → round-trip - No preferences stated → omit filters - Specific time requested (e.g., "after 10pm") → use time range - Broad time preference (e.g., "morning flights") → use time blocks | Read-only |
| flights_search_anywhere | Discovers cheapest flight destinations from an origin city when the user has no specific destination in mind. Use for open-ended queries like 'where should I go?', 'cheapest flights from Dubai', 'surprise me', or 'best deals from Singapore'. Returns up to 15 cheapest destinations with prices, airlines, and travel dates. Do NOT use when user has a specific destination — use flights_search instead. Use IATA city codes from places_find_location. | Read-only |
| holidays_lookup | Looks up public holidays for a country within a date range. Used for travel planning to find local holidays at the destination. | Read-only |
| hotels_get_photos | Gets photos for one or more hotels (up to 8), up to 3 per category: rooms, bathrooms, dining, amenities such as the pool and gym, public spaces such as the lobby, exterior, views and nearby attractions. Hotels with no categories get up to 12 photos with no category. Use this tool for room photos too, because hotels_get_rooms gives only one image per room type. Use categoryFocus to show some categories first. missingHotelIds lists the hotels that could not be loaded. | Read-only |
| hotels_get_rooms | Gets room rates for a specific hotel. Returns room types with pricing from multiple providers. Each rate's perNight price covers all rooms in the search together, for one night. Requires hotelId and searchId from a prior hotels_search call. If status is "incomplete", more rates are still loading: wait pollAgainInSeconds and call once more with the same arguments. | Read-only |
| hotels_search | Searches for hotel accommodations by city, geo-location, or hotel ID. Not for restaurants, activities, car rentals, or non-travel queries. Use places_find_location first to get codes/IDs/coordinates. Each hotel price is per night for all rooms in the search together. With 2 rooms, a price covers both rooms. Polling flow: 1. First call with search params (no searchId) → creates search session, returns searchId immediately (status: "created", pollAgainInSeconds: 5). 2. Wait pollAgainInSeconds, then call again with searchId → returns hotel results with status "incomplete" (better rates still arriving, pollAgainInSeconds says when to call again) or "complete" (all providers have answered). 3. While status is "incomplete", wait pollAgainInSeconds and call again. Stop when status is "complete". If it is still "incomplete" after 3 reads, use the results you have. Once a search is complete, every read (new filters, sorting or pagination) returns status "complete" at once. Search types (one per new search): 1. citySearch — Hotels in a city. Suitable for generic proximity queries (e.g., "near airports" or "downtown") when combined with sorting. 2. geoSearch — Hotels near a specific named location. Suitable when the user specifies a particular airport, landmark, or POI. Recommended radius: 10km for landmarks, 20km for airports. 3. hotelSearch — Single hotel by ID. Proximity guidance: - Generic proximity (e.g., "hotels near airport") → citySearch + "distance_from_nearest_airport_asc" sorting - Generic city center (e.g., "downtown hotels") → citySearch + "distance_from_center_asc" sorting - Named location (e.g., "hotels near Changi Airport") → geoSearch with POI coordinates + "distance_asc" sorting - Explicit radius (e.g., "hotels within 15km of Eiffel Tower") → geoSearch with POI coordinates and radius Integration with places_find_location: - citySearch: get cityCode with types=["city"] - geoSearch: get coordinates with types=["poi"] Examples: New search: { citySearch: { cityCode: "DXB" }, checkIn: "2025-11-06", checkOut: "2025-11-07", rooms: [{ adultsCount: 2, childrenCount: 0 }], sorting: "price_asc", currencyCode: "USD" } Refinement: { searchId: "abc123", filters: { starRating: { min: 4 } }, sorting: "price_asc", currencyCode: "USD" } Refinement: Provide the searchId from a previous response with updated filters, sorting, or pagination. Refinement replaces all previous filters — re-include existing ones to keep them. Sorting (string): "relevance" (default), "price_asc", "price_desc", "star_rating_asc", "star_rating_desc", "review_score_asc", "review_score_desc", "distance_asc", "distance_from_center_asc", "distance_from_nearest_airport_asc" Filters (flat object): - amenities: hotel property amenities (wifi, pool, parking, gym, etc.) - roomAmenities: room-level features (bathtub, balcony, minibar, free cancellation) - starRating: { min?, max? } — star rating range (0-5) - reviewScore: { min?, max? } — guest review score (0-10) - priceRange: { min?, max? } — price per night for all rooms together (multiply a per-room budget by the number of rooms) - propertyTypes: accommodation type (Hotel, Resort, Apartment, etc.) - brands: hotel brand names (Holiday Inn, Hampton, etc.) - chains: parent chains (Marriott, IHG, Hilton, etc.) Filter options: a page 1 read with searchId carries filterOptions with the amenities, roomAmenities, brands, chains and propertyTypes of this search, partial while status is "incomplete" and final when status is "complete". Page 2 and later reads have no filterOptions. Each entry is { name, count }, where count is the approximate number of hotels in the whole search with that value, before filters. Amenity counts can be lower than the real number. Every listed name is a valid value for the filter of the same name. Use these names in filters on the next read instead of guessing. | Read-only |
| places_find_location | Search for cities, airports, districts, states, hotels, or points of interest by name. Returns location codes, IDs, and coordinates. Supports pagination (default: 10 results per page). PLACE TYPES: Filter by specific types using the 'types' parameter: - city: Major cities (returns cityCode like "DXB", "PAR") - airport: Airports (returns IATA codes like "JFK", "LHR") - district: Neighborhoods within cities (returns districtId) - state: States, provinces, regions - hotel: Individual hotels (returns hotelId) - poi: Points of interest, landmarks (returns coordinates) If 'types' is omitted, returns all matching place types. POI SEARCH WITH LOCATION BIAS: POI search uses Google Places API. You can optionally provide locationBias (approximate coordinates) to improve result relevance when geographic context is known. When to provide locationBias: - User mentions a city: "Eiffel Tower in Paris" (provide Paris coordinates) - Previous conversation context provides location - You recognize the landmark location When NOT to provide locationBias: - No geographic context available - Uncertain about location - Global/ambiguous landmarks EXAMPLES: Find city: { query: "Dubai" } returns cityCode: "DXB" Find district: { query: "Downtown Dubai", types: ["district"] } returns districtId Find airports: { query: "New York", types: ["airport"] } returns JFK, LGA, EWR Find hotel: { query: "Burj Al Arab", types: ["hotel"] } returns hotelId Find POI with bias: { query: "Eiffel Tower", types: ["poi"], locationBias: { latitude: 48.85, longitude: 2.35 } } Find POI without bias: { query: "Marina Bay Sands", types: ["poi"] } Pagination: { query: "hotel", pageSize: 10, page: 2 } returns results 11-20 AMBIGUITY HANDLING: When multiple locations match, response includes hasAmbiguity: true and disambiguationHint. Ask user to specify which location. NOTES: - locationBias is optional (text search works without it) - Approximate coordinates are fine (city-level accuracy) - Location bias improves relevance but doesn't exclude other regions | Read-only |
| places_get_nearest_airport | Finds the nearest airport to given coordinates. Returns airport IATA code, name, and distance. Useful for determining departure airport when only coordinates are known. | Read-only |
Change history
- hotels_search: description changed (+"Filter options: a page 1 read with searchId carries filterOptions with the amenities, roomAmenities, brands, chains and propertyTypes of this search, partial while status is "incomplete" and final when status is "complete". Page 2 and later reads have no filterOptions. Each entry is { name, count }, where count is the approximate number of hotels in the whole search with that value, before filters. Amenity counts can be lower than the real number. Every listed name is a valid value for the filter of the same name. Use these names in filters on the next read instead of guessing.")
- flights_search: description changed (+"Filter options: a page-1 read with searchId returns filterOptions with the airlines, alliances, bookingSites and stopoverAirports found in this search; page 2 and later do not. While status is "incomplete" the lists are partial and can grow; when status is "complete" they are final. Each entry is { code, name, price }, where price is the cheapest per-person price in the search currency, before filters. Every code is a valid value for the filter of the same name. Use these codes in filters on the next read instead of guessing.")
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | com.wego.mcp/mcp | 17 Nov 2026 | 18 Nov 2026 | 1 |