Traveler.md

md.travelerPublished by traveler.mdOfficial publisherv1.1.0Updated Oct 24, 2026

A traveler's portable travel profile and trip plans. It remembers, it does not search or book.

VerifiedStreamable HTTPWeb executableLocation & LifestyleKnowledge & Memory

Overview

AI-generated overview

Gives an assistant a traveler's stored travel profile and trip plans to read and update, so recommendations start from known preferences.

What you can do
Traveler.md stores two kinds of document: a single traveler profile holding stable preferences such as seat choice, hotel style, budget and dining style, and one document per trip holding destinations, dates, itinerary, bookings and notes. Tools let the assistant read, create and update the profile, and list, read, create, update and archive trips. Documents are made of named sections of short sentences, and updates require the version hash from the latest read to prevent silent overwrites. It only remembers; it has no inventory, prices, availability or recommendation engine.
When to use it
Use it when you want an assistant to remember how you like to travel and the details of each trip across conversations, so you do not repeat yourself. It suits planning, shortlisting and organizing trips, not searching or booking them.
Requirements
A remote MCP client that supports streamable HTTP and OAuth 2.1, connected to the hosted endpoint. No API keys or environment variables; on first use a browser window opens so the traveler signs in to Traveler.md and approves the connection.
Before you install
The assistant can write to and archive your travel records, so review changes it makes. Access is granted per client through OAuth and can be revoked from the account page. The server rejects payment card numbers, passport numbers, known traveler numbers, social security numbers and door or access codes, and tools are instructed not to record health, accessibility, dietary or biometric details.

Installation

In SourceWeft

  1. Open Traveler.md in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/md.traveler%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "traveler-md": {
      "type": "http",
      "url": "https://mcp.traveler.md/mcp"
    }
  }
}

README

Traveler.md MCP Server

Traveler.md gives an AI assistant a traveler's own travel memory. It holds a durable profile of how the traveler likes to travel and one plan per trip. The traveler owns the data, authorizes access once, and can revoke it at any time.

This repository describes the hosted MCP (Model Context Protocol) server at https://mcp.traveler.md/mcp. The server source is not published here. The full documentation is at https://docs.traveler.md/mcp.

What the server does

The server stores two kinds of document and returns them on request.

  • traveler.md is the profile. It holds stable preferences: seat choice, hotel style, budget, dining style, travel companions. One per traveler.
  • trip.md is one trip. It holds destinations, dates, itinerary, bookings and notes. Many per traveler.

An assistant reads these before it plans or recommends, so the traveler does not repeat themselves. An assistant writes back what it learns, so the next conversation starts with the same knowledge.

Scope: travel memory only. The server has no inventory, no prices, no availability and no recommendation engine. Your assistant does the recommending. The profile changes what the recommendation is based on.

Tools

ToolPurpose
read_profileReturn the profile, optionally filtered to named sections
create_profileCreate the profile on first use
update_profileChange one or more profile sections
list_tripsPage or search trips by title, content, status or date
read_tripReturn one trip
create_tripCreate a trip with a title and a status
update_tripChange a trip's status, dates, sections or dated events
archive_tripFile a trip away

Every document is a set of named sections. Each section is a list of short sentences. Updates require the version_hash from the most recent read, so two assistants writing the same record cannot overwrite each other silently.

Configuration

The server uses streamable HTTP and OAuth 2.1. There are no API keys and no environment variables. On first use the client opens a browser window. The traveler signs in to Traveler.md and approves the connection.

VS Code and GitHub Copilot

One click:

[Add to VS Code]

Or add this to .vscode/mcp.json in a workspace, or to your user mcp.json:

json
{  "servers": {    "travelermd": {      "type": "http",      "url": "https://mcp.traveler.md/mcp"    }  }}

Other clients

bash
claude mcp add --transport http travelermd https://mcp.traveler.md/mcp   # Claude Codecodex mcp add travelermd --url https://mcp.traveler.md/mcp               # Codex

Any client that speaks remote MCP takes the URL directly:

json
{  "mcpServers": {    "travelermd": {      "url": "https://mcp.traveler.md/mcp"    }  }}

Per-client guides for Claude, Cursor, ChatGPT, Gemini and others are at https://docs.traveler.md/mcp.

Usage

Once connected, ask about travel in plain language. The assistant calls the tools.

You sayThe assistant calls
"Where should we stay in Lisbon?"read_profile, then recommends
"What is my next trip?"list_trips sorted by start date
"What is the plan for Kyoto?"list_trips, then read_trip
"I always want an aisle seat"update_profile
"We booked the ryokan"update_trip
"I would love to see Patagonia one day"create_trip with status Dreaming

Assistants often answer a travel question from the conversation alone and leave the profile unread. Add a standing instruction to your assistant's instruction file so it reads the profile first:

Before you recommend, plan, shortlist or book anything travel-related, call read_profile on the travelermd server. When a specific trip is in play, find it with list_trips and open it with read_trip.

Skills and agent plugin

An Agent Plugin that packages this server together with skills for onboarding, trip interviews, trip organization and post-trip reviews is at https://github.com/TravelAiSolution/traveler-md-agent-plugin. The skills teach an assistant the section names, the sentence caps and the read-before-write loop.

Data and privacy

The traveler owns every record. Access is granted per client through OAuth and revoked from the Traveler.md account page. The server rejects payment card numbers, passport numbers, known traveler numbers, social security numbers and door or access codes. The tools are also instructed not to record health, accessibility, dietary or biometric details. The privacy policy is at https://traveler.md/privacy.

Support

Open an issue in this repository for questions about the server or its tools. For account or security matters, write to [email protected].

License

The README and the files in this repository are licensed under the MIT License. The hosted server is a Traveler.md service. Traveler.md and TravelAI are trademarks of TravelAI; this license grants no rights to use them.

Source: README.md at commit 1624fde

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestOct 13, 2026
  2. v1.0.1Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Traveler integrations

Map Traveler Mcp

Published by GitHub account mfukushim

A virtual-traveler MCP server that lets an assistant move an avatar around Google Maps, report its journey with Street View photos, and post updates to Bluesky.

STDIODesktop only
Location & LifestyleNot validated yetOct 24, 2026