Skip to Content

MCP server overview

The Traveler.md MCP server gives an AI agent secure, scoped access to a traveler’s Traveler.md and Trip.md files. It implements the Model Context Protocol  and is intended to be installed as a connector in any MCP-aware client: Claude, OpenClaw, Hermes, or a custom agent.

It’s memory, not a travel agent

This is the single most useful thing to get straight before you build against it.

The server is the traveler’s memory. It stores what they’ve said about how they travel, and the trips they’re working on. It has no inventory behind it, no prices, no availability, and no recommendation engine. It will never return a shortlist of hotels or a flight to book.

The recommending stays with your agent. What the memory changes is whose taste that recommendation is built on. “Where should we stay in Lisbon?” is still your agent’s question to answer, but answered after a read_profile it comes back with the neighborhood this traveler likes, the room they need, the budget they actually spend, and the fact that they’re traveling with a toddler this year. None of which they should have to type again, into your product or anyone else’s.

This is why the split matters in practice: an agent that files the connector under “booking tool” either waits for a shortlist that never arrives, or skips it entirely on a “where should we stay” turn, which is the exact turn the memory was written for.

What it does

The server exposes tools for the two core jobs an agent needs to do:

  • Read and write preferences. Fetch the traveler’s Traveler.md, create it if it doesn’t exist yet, or update it when the conversation reveals something new.
  • Read and write trips. List trips, read one, create new ones, and update an existing Trip.md as bookings firm up. Finished or abandoned trips can be archived out of the active list — archiving is reversible from the traveler’s portal, and nothing on this server can delete a trip.

A travel agent (human or AI) generally loads Traveler.md once per session and the relevant Trip.md when one is in flight.

See the full list in Tools.

Who it’s for

  • Travelers connecting Claude or another MCP client. Add the server as a connector so the assistant you already use knows how you travel, without being told again every session.
  • Developers building agents. Use the MCP server as the memory layer so your agent doesn’t have to re-implement preference storage, and so the personalization it does have travels with the user rather than being locked in your database.
  • Partner platforms integrating travel personalization without building their own profile system.

How it connects

The server runs at https://mcp.traveler.md/mcp and uses OAuth 2.1 for authentication. Each traveler authorizes the client once, and the client receives a token scoped to that traveler’s data.

Next steps