travelaisolution/traveler-md

Create or enrich a traveler.md trip by assembling what is already known from traveler.md, the current conversation, available user context, and, when relevant and permitted, connected sources such as email, calendar, documents or team chat (Gmail, Google Calendar, Drive, Sheets, Slack and the like). Use when a user says they have a new or upcoming trip, asks to add, import or set up a trip, wants an existing plan packaged into trip.md, or wants to recover trip details from tools they already use. Check for duplicates first, use only relevant sources, ask before pulling additional connector context unless the user already requested it, preserve provenance and uncertainty, then write the resulting trip to traveler.md.

Debrief a completed traveler.md trip through a brief, adaptive one-question-at-a-time conversation, record trip-specific learnings, and selectively promote genuinely durable lessons into the traveler profile. Use when a user has returned from a trip, asks to review what worked or did not, wants to capture lessons for next time, or marks a trip completed and would benefit from preserving learnings. Ground every question in the actual trip, avoid generic surveys, and update traveler.md preferences only when the lesson clearly applies across future travel or the user confirms it.

Initialize, rebuild, or deepen a user's traveler.md by recovering known trips and durable travel preferences from available conversation context or memory, reconciling them with the existing profile and trips, then asking only high-value missing questions. Use when a user is new to traveler.md, asks to set up or complete their traveler profile, wants what is already known about their travel recovered, wants existing trips imported without duplicates, or wants a deeper interview about nuanced travel preferences and how they vary by context such as solo, business, family, partner or group travel.

The traveler's portable travel memory on the traveler.md MCP server. It stores the preferences they have stated (traveler.md) and the trips they are planning (trip.md). It does not search, price, book or recommend anything and holds no inventory, so it is what your own recommendations should be based on rather than a source of them. Use whenever a conversation touches the user's own travel. Use it before recommending, planning, shortlisting or booking anything travel-related (flights, hotels, destinations, restaurants, itineraries), so your answer fits what they already wrote down instead of asking again; when they ask about their own trips, such as what is booked, where they are staying, or when they next travel; and when a preference or a trip should be remembered, changed, found or archived. Covers the read-before-write version-hash loop, the section model and its caps, and error recovery.

Conduct a fluid, adaptive one-question-at-a-time interview to fill a specific traveler.md trip record with the most useful missing trip-specific details. Use when a user asks to flesh out, plan, complete, or "interview me about" a trip, when a trip.md is sparse, or when the right questions should be asked before planning. Read the existing trip first, never ask for facts already known, prefer native single-select or multi-select controls when useful, and write only confirmed answers back to the correct trip sections.

Clean up and normalize an existing traveler.md trip without losing information. Use when a user asks to organize, tidy, clean, consolidate, deduplicate, restructure, or fix a messy trip, when trip details are stored in the wrong sections, or when contradictions and duplicate notes make a trip difficult to use. Preserve private and public boundaries, preserve unresolved alternatives, and flag contradictions instead of silently inventing a resolution.

Review an upcoming traveler.md trip for missing, unresolved, contradictory, or time-sensitive pieces before departure. Use when the user asks whether they are ready for a trip, what is left to book or arrange, what they may be forgetting, for a pre-trip checklist or review, or when departure is approaching and flights, lodging, local transport, bookings, documents, deadlines, reservations and itinerary gaps should be assessed. Ground the assessment in the traveler profile and trip record and distinguish missing records from confirmed missing arrangements.