Server Details
Aggregated travel MCP — flights, tours, activities, price checks, visas, and more.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
39 toolsairlines_lookupInspect
Look up an airline by IATA (2-char) or ICAO (3-char) code.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes |
airlines_searchInspect
Search airlines by name. Returns up to 20 results.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| country | No | ||
| active_only | No |
airports_lookupInspect
Look up an airport by IATA (3-char) or ICAO (4-char) code. Returns full details including runways.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes |
airports_nearInspect
Find airports near a geographic point. Returns results sorted by distance.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| latitude | Yes | ||
| longitude | Yes | ||
| radius_km | No | ||
| include_small | No |
airports_searchInspect
Search airports by name or city. Returns up to 20 results sorted by size.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| country | No | ||
| type_filter | No |
data_statusInspect
Check which static datasets (airports, airlines, visas) are loaded and their row counts.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
fcdo_list_countriesInspect
[fcdo] List all countries with UK FCDO travel advice.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
fcdo_travel_adviceInspect
[fcdo] Get UK FCDO travel advice for a specific country. Includes safety, entry requirements, health, and warnings.
| Name | Required | Description | Default |
|---|---|---|---|
| country | Yes |
kiwi_feedback-to-devsInspect
[kiwi] Send feedback to the dev of the Kiwi MCP server.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The content of the feedback. Don't hesitate to include any text relevant to the issue (logs, error message) if you are having one. |
kiwi_search-flightInspect
[kiwi]
Search for a flight
Description
Uses the Kiwi API to search for available flights between two locations on a specific date.
How it works
The tool will:
Search for matching locations to resolve airport codes
Find available flights for the specified route and date range
Method
Call this tool whenever a user wants to search for flights, regardless of whether they provided exact airport codes or just city names.
You should display the returned results in a markdown table format: Group the results by price (those who are the cheapest), duration (those who are the shortest, i.e. have the smallest 'totalDurationInSeconds') and the rest (those that could still be interesting).
Always display for each flight in order:
In the 1st column: The departure and arrival airports, including layovers (e.g. "Paris CDG → Barcelona BCN → Lisbon LIS")
In the 2nd column: The departure and arrival dates & times in the local timezones, and duration of the flight (e.g. "03/08 06:05 → 09:30 (3h 25m)", use 'durationInSeconds' to display the duration and not 'totalDurationInSeconds')
In the 3rd column: The cabin class (e.g. "Economy")
(In case of return flight only) In the 4th column: The return flight departure and arrival airports, including layovers (e.g. "Paris CDG → Barcelona BCN → Lisbon LIS")
(In case of return flight only) In the 5th column: The return flight departure and arrival dates & times in the local timezones, and duration of the flight (e.g. "03/08 06:05 → 09:30 (3h 25m)", use 'return.durationInSeconds' to display the duration)
(In case of return flight only) In the 6th column: The return flight cabin class (e.g. "Economy")
In the previous-to-last column: The total price of the flight
In the last column: The deep link to book the flight
Finally, provide a summary highlighting the best prices, the shortest flights and a recommendation. End wishing a nice trip to the user with a short fun fact about the destination!
| Name | Required | Description | Default |
|---|---|---|---|
| curr | No | Currency for response (examples: EUR, USD, GBP, JPY, CAD, AUD, NZD, CHF etc.) | EUR |
| sort | No | Sort results by: price, duration, quality or date (default: date) | date |
| flyTo | Yes | Location to fly to: It could be a city or an airport name or code | |
| locale | No | Language of city names and kiwi.com website links (examples: en, uk, de, fr, es, it, ru etc.) | en |
| flyFrom | Yes | Location to fly from: It could be a city or an airport name or code | |
| cabinClass | No | Cabin class: M (economy), W (economy premium), C (business), F (first class) | |
| passengers | No | Passengers details. The total number of passengers must be between 1 and 9. There must be at least one adult. There must be at least one adult per infant. | |
| returnDate | No | Return date in dd/mm/yyyy format | |
| departureDate | Yes | Departure date in dd/mm/yyyy format | |
| returnDateFlexRange | No | Return date flexibility range in days (0 to 3 days before/after the selected return date) | |
| departureDateFlexRange | No | Departure date flexibility range in days (0 to 3 days before/after the selected departure date) |
peek_experience_availabilityInspect
[peek] Get availability information for a specific experience including dates, times, and pricing
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the experience | |
| endDate | Yes | End date inclusive in YYYY-MM-DD format (e.g., '2025-06-20' would return things taking place ON or BEFORE the 20th) | |
| quantity | Yes | Number of travelers | |
| startDate | Yes | Start date inclusive YYYY-MM-DD format (e.g., '2025-06-19') |
peek_experience_detailsInspect
[peek] Get detailed information about a specific experience by ID
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the experience to retrieve |
peek_list_tagsInspect
[peek] List all category tags
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
peek_render_activity_tilesInspect
[peek] Render activity tiles for a list of activity IDs, returning an embeddable widget URI
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID or comma separate list of activity IDs to render as tiles |
peek_search_experiencesInspect
[peek] Search for travel experiences with comprehensive filtering options. Returns available categories, tags, and regions with IDs for further filtering.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | When the user wants something w/ a specific keyword (bike, beer, art, etc) limit to experiences whose title contain a keyword. Never include location information. | |
| tagId | No | When you have determined the user is interest in a specific vibe of activity (family friendly, romantic, etc) limit to only experiences with a specific tag (single tag ID) | |
| latLng | No | When the user wants something NEAR a specific place, but not necessarily IN a specific place, limit to only those near a given lat_lng. ex: "37.7799,-122.2822". Don't use this for regions, instead use the search_regions and provide a region id. this is a good fallback if a specific region is lacking inventory. | |
| endDate | No | Return experiences that are available on or before this date in YYYY-MM-DD format (e.g., '2025-06-20' would return things taking place ON or BEFORE the 20th) | |
| regionId | No | When you have determined the user wants something in a specific region (found w/ search_regions) limit to only a specific region ID | |
| startDate | No | Return experiences that are available on or after this date. YYYY-MM-DD format (e.g., '2025-06-19') | |
| categoryId | No | Limit to only a specific activity category |
peek_search_regionsInspect
[peek] Search for regions by name
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of regions to return (default: 50) | |
| query | Yes | Search query to match against region names |
restcountries_country_infoInspect
[restcountries] Look up country information from REST Countries.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| fields | No | ||
| search_by | No | name |
tourradar_algolia-operator-searchInspect
[tourradar] Use this when you need to find a tour operator's ID by their name for filtering tours.
Searches tour operators by name and returns matching operators with their IDs. Use the returned operator ID with tour search filters.
| Name | Required | Description | Default |
|---|---|---|---|
| textSearch | Yes | Operator name for search, for example `Topdeck` |
tourradar_b2b-cities-searchInspect
[tourradar] Use this when you need to find city IDs for tour search filters like start city, end city, or cities to visit.
Searches for cities by name within a specific country. Supports multiple name variants to handle different spellings (e.g., Krakow, Kraków, Cracow).
| Name | Required | Description | Default |
|---|---|---|---|
| search | Yes | City name filter. It is recommended to use this filter to narrow down the search results. Please use english only names. How to search: If you are looking for Kraków city, please pass potential candidates here, like: ['Krakow', 'Kraków', 'Cracow']. It will return all cities that match any of the names. | |
| country_code | Yes | ISO 3166-1 alpha-2 country code (e.g., 'US' for USA, 'GB' for United Kingdom, 'DE' for Germany). |
tourradar_b2b-continents-listInspect
[tourradar] Use this when you need continent IDs for filtering tours by region.
Returns a list of all supported continents with their IDs and names for use in tour search filters.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
tourradar_b2b-countries-listInspect
[tourradar] Use this when you need to look up country IDs for filtering tours or validating country names.
Returns a complete list of all supported countries with their IDs, names, and ISO country codes.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
tourradar_b2b-currencies-listInspect
[tourradar] Use this when you need to check supported currencies or get currency details like symbols.
Returns a list of all supported currencies with their codes (USD, EUR), names, and symbols ($, €).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
tourradar_b2b-languages-listInspect
[tourradar] Use this when you need language IDs for filtering tours by guide language.
Returns a list of all supported languages with their IDs, codes, and names for use in tour search filters.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
tourradar_b2b-operator-detailsInspect
[tourradar] Use this when the user wants information about a tour operator, such as their terms and policies.
Fetches operator details including name, code, and terms & conditions based on operator ID.
| Name | Required | Description | Default |
|---|---|---|---|
| operatorId | Yes |
tourradar_b2b-tour-departuresInspect
[tourradar] Use this when the user asks about available departure dates, pricing for specific dates, or needs to validate if a departure date is available.
Returns a list of departures for a specific tour within a date range, including availability status, pricing, and booking information.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number. Default is 1 | |
| tourId | Yes | Tour ID | |
| dateRange | Yes | Returns only departure dates in the desired range |
tourradar_b2b-tour-detailsInspect
[tourradar] Use this when the user wants to see detailed information about a specific tour.
Fetches comprehensive tour details including itinerary, pricing, operator info, images, and booking links based on tour ID.
| Name | Required | Description | Default |
|---|---|---|---|
| tourId | Yes |
tourradar_b2b-tour-faqInspect
[tourradar] Use this when the user has questions about a tour that might be answered in the FAQ section.
Returns a paginated list of frequently asked questions and answers about a specific tour, covering topics like inclusions, requirements, and policies.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number. Default is 1 | |
| tourId | Yes |
tourradar_b2b-tour-mapInspect
[tourradar] Use this when the user wants to see tour routes on a map or compare itineraries visually.
Fetches tour details for one or more tours and prepares map data with all itinerary locations, coordinates, and day-by-day information for visual display.
| Name | Required | Description | Default |
|---|---|---|---|
| tourIds | Yes |
tourradar_b2b-tour-types-listInspect
[tourradar] Use this when you need tour type IDs for filtering tours by category like adventure, cultural, or wildlife.
Returns a hierarchical list of tour type groups and their individual types with IDs and names.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
tourradar_general-current-dateInspect
[tourradar] Use this when you need to know the current date, especially before setting departure date filters.
Returns the current date and time in ISO format. Essential for calculating valid date ranges for tour searches.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
tourradar_vertex-tour-searchInspect
[tourradar] Use this when the user describes what they want in natural language and you need AI-powered semantic search to understand their intent.
Before use this tool, please READ all possible filters. PLESE USE FILTERS, when can be used, to make search faster and much more precise. Please use start_city, end_city, cities, countries, start_country, end_country filters if possible. You can use multiple of them.
AI-powered semantic search for tours using natural language queries combined with optional filters. Uses Google Vertex AI to understand intent and find relevant tours based on descriptions, themes, or specific requests.
Use vertex-tour-search when:
The user describes what they want in natural language
You need semantic/AI-powered search to understand intent
Combining natural language with filters for refined results
Examples:
"Family-friendly safari with kids under 12"
"Romantic honeymoon trip with beach and mountains"
"Adventure tour with hiking and camping for beginners"
"Cultural immersion experience with local homestays"
"Wine tasting tour through European countryside"
Input
Required
textSearch: Natural language description of what the user is looking fordisplay_mode: How to display results —"listing"(default, carousel of tour cards) or"map"(interactive map view)
Optional Filters
Location Filters
Filter | Type | Description |
| string[] | Country where tour BEGINS (ISO 3166-1 alpha-2 codes). OR logic. |
| string[] | Country where tour ENDS (ISO 3166-1 alpha-2 codes). OR logic. |
| number[] | City IDs where tour starts. Use |
| number[] | City IDs where tour ends. Use |
| object | Countries visited DURING the itinerary. Supports AND/OR operator. |
| object | Cities visited on the itinerary. Supports AND/OR operator. |
Range Filters
Filter | Type | Description |
|
| Tour length in days |
|
| Maximum group size range |
|
| Minimum group size range |
|
| Price range (currency: "EUR") |
AND/OR Filters
These filters support both AND and OR operators:
Filter | Values | Description |
| YYYY-MM strings | Filter by departure months |
| ISO 3166-1 alpha-2 codes | Countries visited during itinerary |
| City IDs | Cities visited on itinerary |
Structure: { values: [...], operator: "AND" | "OR" }
OR(default): Tour matches ANY of the specified valuesAND: Tour must match ALL specified values
Examples
Simple text search
{ "textSearch": "family adventure with wildlife" }With location filters
{
"textSearch": "hiking adventure",
"start_country": ["DE", "AT"],
"countries": { "values": ["IT", "CH"], "operator": "AND" }
}With range filters
{
"textSearch": "luxury beach vacation",
"duration": { "min": 7, "max": 14 },
"price": { "min": 2000, "max": 5000, "currency": "EUR" },
"max_group_size": { "min": 1, "max": 16 }
}With departure dates
{
"textSearch": "northern lights tour",
"departures": { "values": ["2026-01", "2026-02", "2026-03"], "operator": "OR" }
}Map display mode
{
"textSearch": "hiking tours in the Alps",
"display_mode": "map",
"countries": { "values": ["AT", "CH"], "operator": "OR" }
}Response
Returns a list of tours matching the query, each containing:
Tour ID, name, and URL
Operator information
Brief description matching the query context
| Name | Required | Description | Default |
|---|---|---|---|
| price | No | Filter by tour price. E.g., { min: 500, max: 2000, currency: 'EUR' } finds tours priced between €500 and €2000. Min and max value cannot be this same. | |
| cities | No | Filter tours by cities visited on the itinerary. City IDs can be obtained from the b2b-cities-search tool | |
| duration | No | Filter tours by duration in days. Example: set min: 5 , max: 8 to find duration between those days. Include this filter when is needed | |
| end_city | No | City IDs where the tour ends (e.g., [1234, 5678]). Use b2b-cities-search to find city IDs. If passing multiple values, will find tours ending in any of the given cities | |
| countries | No | Filter by countries visited DURING the tour itinerary. Use 'start_country'/'end_country' for departure/destination countries. | |
| departures | No | Filter tours by available departure months | |
| start_city | No | City IDs where the tour starts (e.g., [1234, 5678]). Use b2b-cities-search to find city IDs. If passing multiple values, will find tours starting in any of the given cities | |
| textSearch | Yes | ||
| end_country | No | Filter by the country where the tour ENDS (final destination). ISO 3166-1 alpha-2 codes (e.g., ['IT', 'FR']). Multiple values = OR logic. Use 'countries' filter for countries visited during the itinerary. | |
| display_mode | No | How to display the search results. 'listing' shows a carousel of tour cards. 'map' shows tours on an interactive map. | listing |
| operator_ids | No | Filter tours by specific operator ids. You can add multiple operator ids, then OR operator will be used. For lookup for partner by name, please use algolia-operator-search tool. | |
| start_country | No | Filter by the country where the tour BEGINS (departure point). ISO 3166-1 alpha-2 codes (e.g., ['DE', 'AT']). Multiple values = OR logic. Use 'countries' filter for countries visited during the itinerary. | |
| max_group_size | No | Filter by tour's maximum group size. E.g., { min: 1, max: 20 } finds small group tours with max 20 participants. Min and max value cannot be this same. | |
| min_group_size | No | Filter by tour's minimum group size. E.g., { min: 1, max: 1 } finds tours that accept solo travelers. Min and max value cannot be this same. |
tourradar_vertex-tour-title-searchInspect
[tourradar] Search for tours by title using AI-powered semantic search. Returns a list of matching tour IDs and titles. Use this when you need to look up a tour by name. When you know tour id, use b2b-tour-details tool to display details about specific tour
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Tour title or partial title to search for |
tourradar_web-tour-bookingInspect
[tourradar] Use this when the user explicitly wants to book a tour and has provided their contact details.
Creates a booking request for a specific tour. Requires real contact details (email, names; phone optional). Always confirm the departure date by checking departures first. Never fabricate or assume user data - always ask for missing information.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Customer email address. If email is not given by the customer, please ask him before executing this endpoint. Never generate email by yourself, always ask customer for give the email before calling this tool. | ||
| tourId | Yes | Tour ID | |
| lastName | Yes | ||
| firstName | Yes | ||
| paxAdults | Yes | Number of the adults. Always ask customer for this information, is important to have it | |
| paxChildren | Yes | Number of the children | |
| phoneNumber | No | Customer phone number in E-164 format. Is optional, but recommended to provide it. Never put fake phone number, always ask customer for give the phone number before calling this tool. If customer do not gives phone number, just skip this field | |
| departureDate | Yes | Departure date, from customer selection | |
| agentInformation | Yes | Agent information about the booking. Describe here what customer is looked for, preferences etc, what you can recognize. Will be helpful for our Customer Support team to understand the customer needs. | |
| extraInformation | Yes | Customer extra information from the customer or agent. Fill here if customer has provided any additional information about the booking. This is optional and can be empty. |
tourradar_web-tour-send-brochureInspect
[tourradar] Use this when the user requests a tour brochure or PDF to be sent to their email.
Sends a tour brochure (PDF file) to the specified email address. Before using this, ensure the user has provided their email address. If not provided, ask the user for it. Never generate or assume email addresses.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | User email address. If email is not given by the user, please ask him before executing this endpoint. Never generate email by yourself, always ask user for give the email before calling this tool. | ||
| tourId | Yes | Tour ID |
travel_agentInspect
Ask a travel question in natural language. Routes to the right tools automatically and returns a combined answer. Example: 'Cheapest flights from Zurich to Rome next week, and do I need a visa?'
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
visa_checkInspect
Check visa requirement for a passport country visiting a destination.
| Name | Required | Description | Default |
|---|---|---|---|
| passport | Yes | ||
| destination | Yes |
visa_summaryInspect
Overview of visa-free access for a passport country — counts by category.
| Name | Required | Description | Default |
|---|---|---|---|
| passport | Yes |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!