Skip to content

Plan your trip in ChatGPT or Claude

Connect moldova.travel to your AI assistant and ask for a route. It finds real places, checks opening hours and dates, puts the stops in order and gives you a link to share, with a PDF.

The server address

The only address you need. Copy it into ChatGPT or Claude:

https://moldova.travel/mcp
Cost
Free.
Account and key
None. Authentication: none.
What it can do
Read the catalogue and save a trip for you. It books nothing and asks for no money.
Suggested name
moldova-travel

Connect, step by step

ChatGPT

ChatGPT links outside servers through a connector, in developer mode. It is an official setting; nothing is installed. It works on Plus, Pro, Business, Enterprise and Education accounts, in the browser.

  1. Open Settings → Security and login and turn on Developer mode.
  2. Open Plugins and press the + button to create a developer-mode app.
  3. Enter the name Moldova Travel and paste the server address above into MCP server URL. The address ends in /mcp.
  4. If you are asked for authentication, choose No authentication.
  5. Check the list of tools it found and confirm. The app appears among yours.
  6. In a new chat press +, choose Developer mode and select Moldova Travel.

ChatGPT asks you to confirm before it calls a tool that writes. Here there are only two, plan_itinerary and build_itinerary, and that is expected. ChatGPT moves its menus often: if you cannot find a name, search for it in Settings. On work or school accounts an administrator can switch developer mode off.

Claude (claude.ai, Desktop and Cowork)

  1. Open Customize → Connectors.
  2. Press + Add, then Add custom connector.
  3. Enter the name Moldova Travel, paste the server address and press Continue.
  4. Press Continue on the authentication screen, choose No sign in and press Add.
  5. In a chat press + at the lower left, choose Connectors and switch on Moldova Travel.

A free account can have one custom connector. On Team and Enterprise an owner adds it first, under Organization settings → Connectors; members then connect it under Customize → Connectors.

Claude Code

Run the command in a terminal. The server appears in the tool list straight away.

claude mcp add --transport http moldova-travel https://moldova.travel/mcp

Use claude mcp list to see whether it is connected. Add --scope user to have it in every project.

Another client

Any MCP client that speaks HTTP (streamable HTTP) works with the address above and nothing else: no account, no key, no OAuth.

What to ask

Write as to a friend who knows Moldova. The more you say (days, where you start, car or not, what you like), the better the route.

  • “Make me a 3-day route through Moldova in May, with wineries and a monastery, starting from Chișinău.”
  • “What events are on next weekend, within an hour of Chișinău?”
  • “We are four friends with a rental car. We want a day at Orheiul Vechi and a tasting in the afternoon. Put the stops in order and tell me how far we drive.”
  • “What can I visit on a Monday morning in the north, when many places are closed?”
  • “Compare the two-day tour packages and tell me which is cheapest.”

Claude (and other clients that show MCP prompts) also offers the plan_trip prompt (days, interests, date, region, number of travellers), which puts the whole flow in one form.

What you get

A link to share
The route page, day by day, with a map. Anyone with the link can open it.
A PDF
The same route, ready to print or send.
Links to hosts
Every stop has its own link, so you book directly with the host, organiser or tour operator.

How the assistant builds the route

The assistant takes these steps itself, in this order. You do not need to know the names, but they show where the answers come from.

  1. find_place — finds the starting point and its coordinates
  2. search_locations — looks for places open that day, near the route
  3. whats_on — adds the events on the chosen days
  4. plan_route — puts the stops in order and estimates the drive between them
  5. build_itinerary — saves the route and gives you the link

Distances and driving times are estimates, not GPS. Prices are indicative. If a place is closed on the chosen day or an event is on another date, the answer carries a warning the assistant should fix.

Tools

22 tools in four groups. There is also a conversation template, plan_trip (days, interests, date, region, number of travellers), and two resources: the list of regions, moldova://regions, and the planning guide, moldova://how-to-plan.

Tool names and descriptions are in English, the language of the protocol. The public data (locations, events, guides) comes in Romanian and the assistant translates it; build_itinerary, plan_itinerary, get_itinerary and the older tools also take a lang parameter (ro or en). A question mark after a parameter means it is optional.

Build the trip · 6
find_place
A place name to its location, region and coordinates, from our catalogue and the region centres. Use it before any distance or route: coordinates never come from memory.
Parameters: name, kinds?, limit?
plan_route
Puts up to 12 stops in a short visiting order and returns the legs (each names its source: road or an estimate) and totals. Saves nothing.
Parameters: stops[ kind, id ], start { lat, lng }?, returnToStart?, optimize?
travel_between
How far and how long from one place to another, by car, on foot or by public transport, with the source of the figures; says plainly when there is no public-transport data. Each end is a place, a point or a name.
Parameters: from { kind, id } | { lat, lng } | { name }, to { kind, id } | { lat, lng } | { name }, mode?
build_itinerary
Saves the trip you assembled, day by day. Checks that every stop is published and open, proposes times, warns about clashes, and returns a share link, a planToken and a tracked goUrl for each stop. Instant: no AI call on our side.
Parameters: days[ date?, stops[ kind, id, startsAt? ] ], startDate?, lang?
plan_itinerary
Asks our own AI planner for a trip. Runs in the background and returns a planToken; the shared daily budget applies. Prefer build_itinerary.
Parameters: days, partySize, transport, budget?, interests?, travelStartDate?, lang?
get_itinerary
Reads a trip back by its planToken: the progress of a plan_itinerary call and then its itineraries, or a build_itinerary trip with its share link, PDF and map.
Parameters: planToken?, sessionId?, lang?
Search · 8
search
Free-text search over everything published: locations, events, tours, regions, articles and guides. Returns ids such as location:12 or guide:slug, in the shape ChatGPT expects.
Parameters: query
search_semantic
Search by meaning: the locations, events, tours and articles most like what the traveller describes in their own words ("quiet, with children, near water"), each with a similarity from 0 to 1 and the same item the other searches return.
Parameters: query, lang?, kinds?, limit?, nearLat?, nearLng?, radiusKm?, region?
search_locations
Locations by text, region, category, traveller type, price, distance from a point and opening hours on a day or at a moment, with coordinates, address and weekly hours.
Parameters: text?, region?, category?, audience?, price?, nearLat?, nearLng?, radiusKm?, lodging?, openOn?, openAt?, page?, pageSize?
search_events
Events by period (past editions on request), text, region and distance, with venue, coordinates and times in UTC and Chișinău time.
Parameters: text?, region?, from?, to?, on?, includePast?, nearLat?, nearLng?, radiusKm?, page?, pageSize?
search_tours
Tour-operator packages by text, distance and maximum indicative price.
Parameters: text?, nearLat?, nearLng?, radiusKm?, maxPrice?, currency?, page?, pageSize?
whats_on
What is on in a day or a period of up to 31 days: its events and the locations open in it, optionally within a region or a radius.
Parameters: date?, from?, to?, region?, nearLat?, nearLng?, radiusKm?, limit?
list_regions
The tourism regions with code, centre, radius and how many locations and events each holds.
Parameters: none
search_articles
The published articles and question-led guides.
Parameters: text?, kind?, page?, pageSize?
Read · 5
fetch
The full text behind an id returned by search (location:12, event:5, tour:3, region:orhei, article:slug, guide:slug), as { id, title, text, url, metadata }.
Parameters: id
get_location
One location in full: description, weekly hours, seasonal and closure periods, address, coordinates, photos.
Parameters: id?, slug?
get_event
One event in full, by id or slug.
Parameters: id?, slug?
get_tour
One tour package in full, with its route stops in order, by id or slug.
Parameters: id?, slug?
get_article
One article or guide as plain text, partner links as tracked goUrl.
Parameters: slug, kind?
Older, still active · 3
search_experiences
Older catalogue search. Prefer search_locations; the site's own chat still uses this one.
Parameters: lang?, region?, category?, price?, audience?, page?, pageSize?
get_events
Older list of upcoming events. Prefer search_events or whats_on.
Parameters: lang?, page?, pageSize?
get_package
Older package reader. Prefer get_tour.
Parameters: id, lang?

Limits and personal data

Requests

120 requests per minute, per IP address.

The two tools that write, plan_itinerary and build_itinerary, have a smaller limit: 20 calls a minute, per address.

ChatGPT and Claude call from their own servers, so many users share one address and part of the limit is shared. Past it you get a 429 with a Retry-After header: wait and ask again.

Plans
Our own AI planner (plan_itinerary) has a budget of at most 100 plans a day for all assistants together, and a single address may use at most 20% of it. A route the assistant builds with build_itinerary makes no AI call on our side and counts as a tenth of a plan. A plan or a route can be read back with get_itinerary and its planToken for 7 days.
Personal data
The server asks for and keeps no name or e-mail. Do not put personal data in a request: anyone with a route link can open it. Each call is logged without the IP address: the tool, the duration and the outcome.
Links
The only link that reaches a partner is goUrl, a tracked redirect of the platform. The assistant must use it unchanged; partners' phone numbers, e-mails and websites never appear in the answers.
Prices
Indicative, supplied by partners, never a quotation.

If something does not work

I get a 429 error

You passed the address's request limit. Wait the number of seconds in Retry-After (usually a minute) and ask again.

I get PLAN_LIMIT_REACHED

The daily budget of AI plans is used up, this address has had its share, or too many routes were saved in a minute. Ask the assistant to build the route itself with build_itinerary, which costs far less, or try tomorrow.

The connector does not show in the chat

Switch it on from the “+” menu of a new chat. A chat opened earlier does not see it.

I cannot find “Developer mode” in ChatGPT

It exists on Plus, Pro, Business, Enterprise and Education accounts, not on free ones. At work or school an administrator can switch it off.

The assistant gives a link that is not ours

The only link that reaches a partner looks like /go/… on this site. Ask it to use that one unchanged.

The AI plan stays “in progress” or cannot be found

A generated plan takes 20–60 seconds: ask it to check again. If get_itinerary says it cannot find the plan, the token is wrong or older than 7 days. A route built with build_itinerary is ready at once.

More

This page, as MarkdownFor assistants: the same page as plain text. llms.txtThe site guide for AI assistants. Public API v1The same data as plain JSON, without MCP.

Not using an AI assistant? Plan straight on the site, free.

Experiences