What is Traveler.md

Traveler.md is a single markdown file that holds one traveler’s preferences. It is the source of truth for how you like to travel, and it belongs to you, not to any app that reads it.

The idea is deliberately small. Instead of every booking site, airline, and AI assistant keeping its own half-complete picture of you, there is one file. You bring it with you. A new agent reads it and already knows you take the window seat, fly direct when the trip is short, and don’t eat meat.

The shape, at a glance

A Traveler.md file is plain markdown with conventional sections. An agent can parse it reliably; you can open it and fix a line when something changes.

# traveler.md
 
## Profile Overview
 
Travels mostly for pleasure, a few trips a year, usually with a partner.
 
## Flight Preferences
 
- Prefers an aisle seat, ideally in the exit row.
- Avoids red-eye departures.
 
## Accommodation Preferences
 
- Prefers a high floor on the quiet side of the building, king bed.
 
## Food and Dining Preferences
 
- Prefers vegetarian menus.

How agents use it

Agents never touch the file on disk. They connect to the Traveler.md MCP server, which owns storage, enforces the scopes you granted, and hands back parsed structured data. One file, one interface, any number of agents, each working from the same starting picture of you.

What it is not

• Not a trip log. Anything tied to one journey (dates, bookings, itineraries) lives in Trip.md, not here.
• Not a booking system. Agents and partners do the booking. Traveler.md shapes how they book.
• Not a marketing profile. It’s a memory artifact for travel decisions, not an identity record or an ad-targeting dossier.