FREETOUR.com MCP Server for ChatGPT
By FREETOUR.com
Overview
Discover and book free walking tours, guided experiences, activities, day trips, and attraction tickets around the world with FREETOUR.com. Explore more than 21000 tours, activities, and attractions across 2200 destinations in 150 countries. Search by destination, date, language, price, rating, or tour type. Compare options, check availability, and explore tour details, schedules, meeting points, reviews, and pricing. From tip-based free walking tours with local guides to food tours, cruises, nature experiences, day trips, and paid attractions, FREETOUR.com helps you find things to do that fit your trip, interests, and budget.
How to connect
- ChatGPT: Open the FREETOUR.com listing in the ChatGPT app directory and choose Connect. ChatGPT listing FREETOUR.com exposes 2 tools here.
Tools
search_tours
ChatGPTcategories only when the user asks for a specific tour type. Search by city, country, date range, start time, duration, guide language, price range, rating and keywords. Always pass locale: en, es, pt, de, fr, or it — the language the user wrote in. Never infer locale from the city. When locale is en (including unsupported user languages), reply in English. UNSUPPORTED USER LANGUAGE (not en/es/pt/de/fr/it): always pass locale: "en". Put only English theme keywords in query (gothic quarter, tapas) — never the user's full sentence or non-English words. Map price, time, duration, category, destination (city/cities/country), and guide-language intent to the matching tool fields — not query. Reply to the user in English; tour cards and widget labels will be in English. START TIME FILTERING (when the user mentions a time or part of day): Use time_from and time_to as integers 0–23 (whole hours only, inclusive). Never put time words in query — use time_from/time_to. Exact hour H ('at 10', 'um 10 Uhr', 'a las 10'): time_from: H, time_to: H. Range A–B ('from 10 to 12', 'between 10am and 12pm'): time_from: A, time_to: B. After H ('after 10', 'from 10am'): time_from: H (omit time_to). Until / before H inclusive ('before 10', 'until 10am'): time_to: H (omit time_from). Morning ('morning', 'morgens', 'matin'): time_from: 0, time_to: 11. Afternoon ('afternoon', 'nachmittags', 'tarde'): time_from: 12, time_to: 16. Evening ('evening', 'abends', 'soir'): time_from: 17, time_to: 23. 12 PM → 12, 12 AM → 0, 3 PM → 15. When time_from or time_to is set and no date is given, also pass date_from (today) so the API can match scheduled events. DATE FILTERING: use date_from and date_to as YYYY-MM-DD. Never put dates in query. Single calendar day ('tomorrow', 'завтра', 'mañana', 'demain', 'on July 3'): set BOTH date_from and date_to to that same day. Day after tomorrow ('післязавтра', 'pasado mañana', 'übermorgen'): same day in both fields. Today ('today', 'сьогодні', 'hoy', 'aujourd'hui'): both fields = today. Explicit range ('from July 1 to July 5', '2026-07-01 to 2026-07-05'): date_from = earlier day, date_to = later day. Next week ('next week', 'наступного тижня'): date_from = Monday, date_to = Sunday of next week. This weekend ('this weekend', 'ці вихідні'): date_from = Saturday, date_to = Sunday. Open-ended start ('tours from July 1' with no end): date_from only — server extends date_to by 7 days. Compute relative dates from the user's local today when calling the tool. DURATION FILTERING (when the user mentions tour length): Use duration_from and duration_to as integers in MINUTES (inclusive). Never put duration words in query. Exact length L ('1 hour', '90 minutes'): duration_from: L, duration_to: L (1h=60, 1.5h=90, 2h30=150). Range A–B ('2-3 hours', 'von 2 bis 3 Stunden'): duration_from: A60, duration_to: B60. At least H ('at least 2h', '2+ hours'): duration_from: H60. Up to H inclusive ('up to 2 hours', 'max 2h'): duration_to: H60. Shorter than H ('under 2h'): duration_to: H60-1. Longer than H ('over 3 hours'): duration_from: H60+1. Short tour: duration_to: 90. Long tour: duration_from: 180. 1–2 hours: duration_from: 60, duration_to: 120. 2–3 hours: duration_from: 120, duration_to: 180. GUIDE LANGUAGE FILTERING (when the user wants tours conducted in a specific language): Use language_codes as an array of ISO 639-1 codes (e.g. ["ja"] for Japanese, ["es"] for Spanish). Never put language names in query — use language_codes. This filters which language the guide speaks; it is NOT the same as locale (widget/response language). NEVER set locale to the guide language — locale is only how the USER wrote their message. Example: user writes in English 'find tours in London in Spanish' → locale: "en", city: "London", language_codes: ["es"] (cards in English, Spanish flag on tour). Wrong: locale: "es" for that query — that translates the card UI to Spanish. Example: 'tours in Japanese' → language_c…Capabilities
Example Prompts
Click any prompt to copy it.
Links
Similar Apps
Listed on MCP App Store
Add this badge to your site or README. It links to this page.
HTML
<a href="https://mcp-app-store.keenethics-labs.com/app/freetour-com"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>
Markdown
[](https://mcp-app-store.keenethics-labs.com/app/freetour-com)






